congrats!

Quite interesting, I hit something similar the other day but couldn't find the reason.
If the stack was the same size for every platform, stack overflow could be caught while developing. I'll see if I can set the stack size to the same (modest) size for all platforms in my engine

damn right

nice!

Exciting! Custom engine I assume?
What's your approach to level editing, do you use a specific tool?

Looks awesome, can’t wait to try. Thanks for sharing!

For more complex cases like returning a dynamic array from a function, arenas are a simple and easy to use solution. That said you do have to put in the effort to make yourself a nice codebase for C to become enjoyable, which is both a curse and a blessing

C# for sure improved a lot with regard to memory management. I would still challenge the "almost always less work than using an unmanaged language" part though.

For this (arguably simple) example, it would look basically the same in C:

Oh, I think I like the 1st one because you can clearly see the dispenser and the belt where the crates should be put. So you instinctively understand that the bot should transport crates from A to B, and that’s already compelling to me

I think I prefer the first one, but not entirely sure why. Perhaps because it shows better the grid based nature of the game, and has visually interesting props?
The idea of making the bot bigger and focusing on fewer things is good though, I’d say

I see. Never used rust or Julia. Used C# where references (ref keyword) work like ref arguments in cpp, and are not allowed in struct or classes.
Using C these days and appreciate the simplicity!

For me the point of ZII is to make things simpler and more straightforward. No need to think about constructors. "Initialize" a whole array at once to a valid state with just = {} or memset to 0.

Works well when composing data structures too, eg node structs can have pointers, null by default

Ah, we’re talking about cpp! Just learned that references in structs are a thing. I was thinking about references in the C pointer sense.
Then indeed they seem incompatible to ZII in this context

I didn’t know you could have class members that store references in cpp, interesting.
Also it seems you can’t assign them first in the constructor (makes sense, you could call other things from in there at which point the non-null guarantees would not hold).

I don’t get your point: you certainly can initialize a reference to zero, then assign it something else later. Is it that you want to avoid null refs at all time?

So you can shift instructions down? Hadn’t noticed, and was doing it manually

How can I test the e clipboard thing?