François Mockers

the border from style is a lot more rich than a `f32` from this PR, and that would mean handling all those cases for rounded corners

I would like to avoid the risk of having `sections` not be in sync with `bidi_corrected`. Would it make sense to remove `pub` from `sections` (and adding accessors), and update...

while marking as deprecated is nice, at this stage of Bevy I would prefer to break directly

couldn't they be imports?

> b) they won't know to look for an MSRV :) Cargo refuses to run if the local Rust version is not recent enough, with a more explicit message than...

Error message like in https://github.com/bevyengine/bevy/issues/5520 is so confusing for someone not used to them

If we add the field in the `Cargo.toml`, its value must be true. Updating it only on release means it would sometimes be false on main, which is not good.

> Hmmmm. I want to keep the render pass spans as they’re commonly useful for understanding performance. The rest I agree with. No... The spans I left as info are...

@cart spans are not only useful for tracing, they also show up in logs, and the "span stack" is displayed by the panic hook

> Spans showing up in logs isn't necessarily something we want in release builds by default. It leaks "internal implementation details" to users running apps in their console / fills...