It makes parsing more complex because { ... } <- ... is similar to { ... }. (The latter is only available with scoped/cleanup at the moment.) The main consequence is misleading parser errors when something inside { ... } is invalid.
It should be fine to just remove {} from the parser and update all of the source files. The , and <- should be sufficient to avoid ambiguity.
This is also a major syntax change, so it might need a separate branch so that the readme isn't misleading to someone who has an older compiler version.
It makes parsing more complex because
{ ... } <- ...
is similar to{ ... }
. (The latter is only available withscoped
/cleanup
at the moment.) The main consequence is misleading parser errors when something inside{ ... }
is invalid.It should be fine to just remove
{}
from the parser and update all of the source files. The,
and<-
should be sufficient to avoid ambiguity.This is also a major syntax change, so it might need a separate branch so that the readme isn't misleading to someone who has an older compiler version.