Carter Anderson

My take is generally still what I discussed here: https://github.com/bevyengine/bevy/issues/12660#issuecomment-2111371565 Specifically, I think we should investigate the viability of the following plan: 1. Make Result systems feel more automatic /...

As a supplement, I think it would also be interesting to investigate an Option extension trait that lets you do this: ```rust fn system() -> Result { let list =...

`ok_or` is different in that it forces you to select and provide an error type. `ok_or()` is not a replacement for the "screw it I just want a value" mindset...

Ditto for `y = list.ok_or("index 1 should exist")?;`. If you omit the `?` it will compile, but because `&str` does not directly implement Error, adding `?` would cause a failure...

(Also just mirroring discord) I do suspect that we may want our own top level general-purpose (anyhow-style catch-all) Bevy error type to allow us to better encapsulate Bevy context (such...

> IMO we can and should start on this today: I've been frustrated by this in the past. I still think we might want to land this all as a...

(if you're saying we should start merging these changes now as they come in) If you're just saying "lets break ground now", I'm fully on board :)

@JoJoJet its worth calling out that the anyhow impl supports this reasonably (using built in rust features), provided you enable the "backtrace" anyhow cargo feature (and run with the RUST_BACKTRACE=1...

We could also consider adding a bevy feature that sets the environment variable for people: ```rust #[cfg(feature = "backtrace")] std::env::set_var("RUST_BACKTRACE", "1") ``` Just verified that this works. Then if/when we...

Yeah I think eventually we'll need a bevy cli tool. But I do want to focus on using existing ecosystem tools where we can. And I also don't want a...