Duffy O'Craven

The print is not needed, even just a tuple-ization triggers the error: ``` module Issue_462_write_should_be_considered_a_rsved_word; import spicy; public type A = unit { on %init { self.b.connect(new B); } var...

Oh, nevermind. The reported syntax error is because sink b; declaration isn't capable of accessing the members of b. I now see that ``` module Issue_462_C_not_B; import spicy; public type...

Was this supposed to be caught in Spicy, or is it fine that the diagnostic is first reported in: `[error] jit: failed to execute compilation action.`

I reopened after confirming that .write is being treated differently. ``` module Issue_467_missing_member_named_self; import spicy; public type A = unit { on %init { self.b.connect(new B); } length: uint8; data:...

I think this deserves to stay open, even if does get deferred before getting it implemented. We can so easily support to_uint taking arguments with content from all Unicode supported...

It would be fine to enforce base

build/bin/spicy-driver Issue_195_in_Nko.spicy < Issue_195_FakeForeign_input.txt where the spicy is like: ``` module Issue_195_in_Nko; import spicy; const Token = /[^ \t\r\n]+/; const Integer = /[0-9]+/; const FakeForeignInteger = /[0-9a-j]+/; # const ForeignInteger...

>> Robin wrote: ... So this would work only for base > code points inside that table, and subtract the block's starting code point from the code points >> it's...

Note in the difference between the two syntax error texts, the larger has: ``` ...std::string& label) -> std::string { hilti::rt::print(hilti::rt::fmt(std::string("%s"), label), true); } ``` which has surfaced the hilti::rt:: qualified...

A short version which reproducibly outputs ``` 3099 /usr/local/etc/tmp/spicy$printf "12\n" | build/bin/spicy-driver ../Issue_210_end_another_way.spicy Issue_210_illegal_instruction.cc:165:137: warning: control reaches end of non-void function static auto __hlt::Issue_210_illegal_instruction::label_then_BCD(std::string& label) -> std::string { label =...