I don't know much about CRDTs so take it with grain of salt.

Your OR-Set example seem to be implemented incorrectly. Try this in demo:
- Add element to A
- B merges from A
- Remove element in A
- B merges from A

I would expect element to be removed in B but it will stay there until B removes it.

How `typed stack trace` is different from regular `stack trace`?

As expected linux build is not working but wine comes to rescue

Just put stuff in buffer and run compute shader. Less interactions with graphics api - more control for you as experienced user

Not sure about THE best, but definitely pretty good. Since it has zig fmt and compile errors instead of warnings.

how would I know if I'm right?

Yea Box::leak works for short lived programs (or if you need to setup something at the start of long running). I meant arenas are hard to use

That's actually really nice and often used strategy for short lived programs.
Or if its not short lived you can free memory in chunks splitted by livetime e. g. Arena Allocators. Sadly its pretty hard to pull of in rust

One way is run script but terminate it if it encountared to many branches. Since it's your language it should be pretty easy to add such ability

Looks like someone already did it github.com/nuIIpointere...

or you can automate it using build.zig (i assume you using zig this year). Trying to do it now myself

Isn't it just undead unluck plot? And already with anime

If you use file shortcut on url it will open web browser. Super usefull

If you thinking in functional terms you can clone person and ask clone your question. It will leave original person's state unchanged