Christian Buttner

There should be no more breaking changes for a while, I just decided to do all of them in advance before this gets merged. I just pushed another major release...

The language has already stabilized quite a bit, any changes to the grammar should be rare (maybe once a year) and localized. I don't expect there to be major breaking...

Alright, so parser updates are okay as long as they don't break queries, and if they do so, only rarely and ideally not much. And if there are new or...

> > The benefit is > > 1. bragging rights; > > 2. control over when updates happen (we only track releases rather than every commit on the default branch,...

Allowing macros to insert defer into parent scope feels like opening a big can of worms. But I think there should be something in this direction. One example I've found...

Maybe one could require a double `@@` prefix to make it clear there is some hidden control flow. Or require to append a special attribute when calling. Just in hopes...

Would emitting a warning also be special casing things? I imagine a separate linter tool could also warn about this then.

Explicitly casting wider? Probably not. Explicitly casting to a narrower type is always a safety issue, but also it's already allowed for all the other types. I guess for an...

Yeah, maybe. I can see this making it a bit safer, for example when you have some code where you need the raw integer ```c3 uint a = (uint)foo_bitstruct; ```...