One good point made is that the ternary op guarantees a result is returned, whereas a statement if doesn’t. This prevents unassigned variable bugs. users.rust-lang.org/t/ternary-op...

I’m also conflicted about this. As a point of comparison, Rust `if` is a ternary operator (it returns a value) but without the ?: syntax (you need to write if{}else{}). So it’s less compact, but solves the debugging issue. I think for C/C++ it’s best to use with e.g. literals, not with complex expr.

Oh ok I saw your other post saying there is 😅

There’s a bug around the triangle isn’t there?

Interesting. Thanks for digging into this. I feel like to some extent observers defeat the purpose of ECS running all to completion like that while still accessing the ECS world. I wonder how much this serializes execution. But that’s a different topic 😇

Thanks for all the details. The command queue tells me there’s at least the gotcha of applying deferred commands. But since that’s mostly automatic now, maybe it’s not too bad.

That looks almost too useful to not be merged upstream? I couldn’t understand why the default you’ve seen people use doesn’t work, nor if there’s any gotcha (frame delay maybe?) to your proposed solution? That looks quite clean in any case.