Isaac Freund

> This mean that the `src/stage1/parser.cpp` is out of sync ? No, on looking at it myself the stage1 parser adhears to the grammar in this case: https://github.com/ziglang/zig/blob/ac546f56eb2b9fd50a69f1d0bda3d0d070b76f52/src/stage1/parser.cpp#L965-L966

> Thank you for pointing out ! > Looking at it again as you pointed out I can see that I failed to understand the code. > Thank you again...

> I'm trying to write a zig parser using CocoR https://ssw.jku.at/Research/Projects/Coco/ and in doing so I'm getting lots of warnings/errors due to grammar ambiguity and recursion, for example `comptime` in...

@ericonr nope, I haven't tried to implement this yet.

Clarified that all clients must ack and rebased onto #87 to avoid conflicts. > If wonder if it would be desirable to change this to a ping/pong mechanism similar to...

The disadvantage to solving this race implicitly through a ping/pong is that clients which for whatever reason make the pong request before get_layer_surface will still be racy. We could certainly...

Opened up #90 to explore the ping/pong alternative approach.

Tweaked the descriptions to clarify that the compositor may create several new outputs at once before sending this event. Also bumped the protocol version to 4 as there was a...

> Is this the intended sequence? Also, another question. Why do we choose this design over the following: Yes, that's the intended sequence. This was chosen mostly for consistency with...

I've been working on river which is a tagging compositor in the same vein as dwm, xmonad, etc. I thought that it would be good to mention that I've created...