BD103

Results 206 comments of BD103

> 2\. Changes from commands completely break this approach because commands are deferred, and the call stack can't be traced to the calling location by the time the command is...

This is close to finished, it just needs a system to track the caller from `Commands`. That's past my capabilities, but hopefully someone else is up for the task!

> I like this and I want it. Should `Commands::add` and `Command::push` be `track_caller` so that custom user commands can provide call tracing? Or would that be something user should...

> at the risk of sounding incredibly pedantic: 24 bytes. `&str` is the pointer and the length, so it is already 16 bytes. Hah, I forgot about wide pointers. Thanks!

I'm marking this as blocked by #13836. Once that gets merged and this gets enough reviews, this can be merged :)

> @BD103 I wouldn’t say this is blocked. In fact. This has the fix in it already so if this is merged the other PR doesn’t need to be. I...

If someone wants to work on this, I got a lot of progress done in #15118. Feel free to adopt it and follow [my advice here](https://github.com/bevyengine/bevy/pull/15118?scrlybrkr=9612f9dd#issuecomment-2348935105) for finishing it.

Awesome, I'm so happy this is finally happening! I opened up https://github.com/TrialDragon/bevy-website/pull/7 in case you agree to remove the trailing comma in the TOML.