SpecificProtagonist

> Then just impl QueryData for &'static mut T I like this. Additionally we still need to store a mutability flag in the `ComponentInfo` and then check it when accessing...

I tried running the various `add_remove` & `insert_simple` benches, but I need to figure out how to turn of frequency scaling for my laptop first (can't get consistent enough results)....

> Personally, I'd rename track_change_detection and gate all tracking behind it. > For hooks, that's a bit harder. Ideally an optional Option parameter, so that people don't have to litter...

To summarize, the difficulty lies in the multithreaded case, as validation and fetching happen on different tasks: 1.1. Speeds up the case that the system runs at the expense of...

> Is it possible to find the Location in Commands::insert, then pass that forward to the actual command? Yep, that would look [like this](https://github.com/SpecificProtagonist/bevy/commit/0eafbcbd430ff5185c8d41b22baacfec8dee1ccf) (you'd also need to do the...

> Should Commands::add and Command::push be track_caller so that custom user commands can provide call tracing? At best that would mean storing the caller location and changing `Commands::apply` to take...

> At least return an error message It does already print a message (as long as `LogPlugin` or equivalent is enabled): ```2024-07-07T19:47:57.668160Z WARN bevy_state::app: States were added to the app,...

Does it make sense to flatten `SystemCursor` into `CursorIcon`? Also, we might want `CustomCursor` to consist of a `Handle` + hotspot for easy use with assets, though that means you...

I've noticed another problem: The parse errors point at line 1, column 1 instead of the actual location.