Fixed with this build, though there may be some underlying issues that weren't resolved: https://builds.sr.ht/~sircmpwn/job/784376
Mind poking around drewdevault.com and seeing if there are any reasons why it would ENOSPC, ~sircmpwn?
Sebastian referenced this ticket in commit dba688e.
They're currently evaluated before @noreturn function arguments, this should be changed for consistency with eg. returns. We should also double-check everywhere else they're run and possibly update the spec to clarify this.
I found this kind of code
Where? harec doesn't allow slicing expressions as object selectors (with the exception of slice assignment, which is special-cased, see section 188.8.131.52), so I don't think this is the case.
why can I compile this code, but got "slice or array access out of bounds"
Slicing expressions don't include the end index - see section 184.108.40.206. Thus, len(x[1..2]) == 1, leading to an error when you try to assign a int to it.
No, the lack of a grammar for the
nulltype is deliberate, see section 220.127.116.11 of the spec.
slicing-expression is special-cased in assignment. We deliberately avoid allowing slicing expressions to be object selectors in the general case in order to simplify the implementation.