Miles Silberling-Cook
Miles Silberling-Cook
We had a good long bikeshed about this last night. This is effectively our current approach (with slightly different keywords): | Semantics | Res | Single | | --------- |...
I'd like to respond to @janhohenheim as well. > Bevy should generally make panicky APIs opt-in, not opt-out. I don't think you should be able to "opt-in" to panicking on...
I think that's a fair decision. I will try to prioritize the work for error-levels, I think that will make this decision a lot easier.
We are seeing a pattern emerge with global observers, which generally looks something like this ```rust world.observe(|target: Trigger, buttons: Query| { if let Some(button) = buttons.get(trigger.entity()) { /// add behavior...
I think it's possible we many be able to sweep this up as part of https://github.com/bevyengine/bevy/pull/16589, or as part of tracing handler follow-up.
This appears to have been resolved at some point. I'm not able to replicate the issue on 0.15.
Ah, interesting. I couldn't replicate on my fallible systems branch. Perhaps the scheduled system change happens to resolve this issue, or perhaps I made a mistake. I'll do more testing.
Chi-squared, Nice! Looks pretty good at a glance, I will have time to review later in the week.
Can anyone still reproduce this? It's quite old.
Bundles themselves are not deprecated, but the existing bundles are being removed from the engine's public api. Required components is actually kind of built on bundles. In the future, the...