Benjamin Bannier

Even though we resolved #674 for `string` values, this still seems broken for other basic types like integers, ```ruby module foo; function inc(inout i: uint8) {++i;} global x = 0;...

If one wants to check whether a `map` contains a value and retrieve it one currently is nudged into a double iteration pattern, e.g., ```ruby global xs: map; xs[0] =...

I would like to turn a data behind a unit field into a reference, e.g., to avoid copying when passing that field on. This works if I introduced a helper...

I would expect that the `skip` in the following unit makes no difference to the parsing behavior: ```ruby module foo; public type X = unit { xs: uint8[]; : skip...

As of b098367a98901c5a29bfad725e17b8ce4830c679 the following incorrect code is not rejected anymore, but instead triggers an exception at compile time: ```ruby # file: foo.spicy module foo; type C = enum {...

It currently seems impossible to introduce nested scopes. ```ruby module foo; function f() { { local x = 1; } } ``` ```console $ spicyc -dj foo.spicy [error] foo.spicy:4:5: syntax...

Consider adding a queue data structure to the Spicy runtime library

1

We should consider adding a queue data structure to the Spicy runtime library. We currently only provide a `vector` and users need to implement their own, if implemented in Spicy...

Type coercion failure when trying to `&parse-from` with `begin(some_stream)`

1

While looking for a workaround for #1523 I ran into a type coercion failure I did not expect. ```ruby module foo; global s = stream(b"\x00\x01\x02"); public type X = unit...

We currently explicitly disallow in the documentation to use `&parse-at` with an external stream. This is not symmetric with `&parse-from` which allows external data. I think it would make sense...

It seems impossible to modify a parameter if it is an unwrapped type i.e., something not inside a `struct` or wrapped in a `strong_ref` like we do for contexts, ```ruby...