You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
calling INT with float bounds results in a crash #26
Indeed. The intention was that indices may be expressions, but must have integer type, but that's not made explicit in the specification. I think we should just make that explicit and also check and report better errors in your examples above.
Activity
[-]calling INT results in a crash[/-][+]calling INT with float bounds results in a crash[/+]mzuenni commentedon Mar 9, 2026
Using a float, or a string as an array index also seems to crash:
eldering commentedon Mar 14, 2026
Indeed. The intention was that indices may be expressions, but must have integer type, but that's not made explicit in the specification. I think we should just make that explicit and also check and report better errors in your examples above.
mzuenni commentedon Mar 15, 2026
For the indices I agree, but what is intended for
INT?Allowing or disallowing this would both be fine for me. (Currently checktestdata crashes => so its not allowed)
eldering commentedon Mar 15, 2026
I think the implicit assumption was that
minandmaxhave integer type, so we should make that explicit and also make the error message more explicit.