Why is this error not identified even with Debug mode and Range checks On

[Ten_Mile_Hike]

Code: Text  [Select][+][-]

1. Environment[Win 11, Laz 4.0RC2, FPC 3.2.2, {$mode objfpc}, Debug mode]

Code: Pascal  [Select][+][-]

1. procedure TForm1.Button1Click(Sender: TObject);
2. type
3.   q = 1..10;
4. var
5.   x: integer;
6.   Mark: set of q;
7. begin
8.   Mark := [5, 11];{<-Why doesn't 11 cause a range check error?}
9.   for x in Mark do Memo1.Lines.add(IntToStr(x) + ' IN Mark');
10. end;

[Thaddy]

Yes, strange. It only fails with assignment, though:

Code: Pascal  [Select][+][-]

1. // mark := [5,11] // should fail, but does not.
2.   mark :=[]
3.   include(mark,5);// OK
4.   include(mark,11)// fails, rangecheck error

OTOH the for in do doesn't see the 11 as part of the set so that behaves correct.
I also tested making the set a type too, but the same behavior: it does not range check the inititial set assignment.
This is a bug indeed, also in 3.3.1.
I will report it with a simplified example.

[Thaddy]

Reported as #41132 with this simplified full program:

Code: Pascal  [Select][+][-]

1. {$mode objfpc}{$H+}{$R+}
2. type
3.   TmyRange = 1..10;
4. var
5.   x: integer;
6.   Mark: set of TmyRange;
7. begin
8.   Mark := [5,11];{<-Why doesn't 11 cause a range check error?}
9.   for x in Mark do write(x,' IN Mark');
10. end.