IntegratedQuantum

> The contents of the "futex" field should had never changed, since it's passed by value and not by reference. This is not true. Zig is allowed to optimize function...

> Any status update with this? At least from my side it's all done and it appears to be all working. I'm also just waiting.

Thanks for pointing out this issue.

@mlugg The compiler crashes for me as well with `attempt to use null value`. Here is the debug error output from the latest master version(`0.11.0-dev.3394+c842deea7`): Expand ``` $ ~/zig/stage3/bin/zig run...

I just updated my zig version and the problem got a lot worse. EDIT: I updated again and it is now back to how it was originally. Expand This simplified...

I never used unreal engine, so you have to clarify what physical effects you mean. Is this just about wind, or are there other effects that you want?

Oh, I see. Some of these are pretty expensive effects. let me just go through them: - collision is already mentioned in #82 - Blast seems to be about realistic...

I think I found something: ```zig /// Returns whether the character is printable and has some graphical representation. /// This also returns `true` for the space character. /// This is...

> Right, it should be noted that `std.ascii.isPrint` **now also considers spaces to be printable**. This is a bit of behavioral breaking change. I'm not talking about the spaces. Also...

I think the distinction between `expected` and `actual` just adds needless complexity. I'd suggest just naming it `first` and `second` to avoid this debate entirely. Of course that would mean...