tbodt

# Stabilization report ## Implementation history - Early history is summarized at https://github.com/rust-lang/rust/pull/72981#issue-630865543 - The libs team decided to defer to the error handling team on the above stabilization PR...

The implementation is made much more difficult by https://github.com/rust-lang/rust/pull/99212 not being available in the bootstrap compiler. If one simply does a partial stabilization, the result won't compile with the bootstrap...

This is also blocked by anyhow's `deny(warnings)`. Stabilizing a feature results in a warning in any crate that uses it, recommending that the `#[feature()]` be removed. But anyhow has `#[deny(warnings)]`,...

It might not actually be necessary to put it all in bootstrap - I got CI to pass. But that's not the full bors CI...

@bors try

> So I've had to make the entire stabilization conditional on `cfg(not(bootstrap))`. Guess I didn't have to! Only had to fix the doctest, it seems.

> I may miss something but does it make sense for `disabled` to be a function as opposed to an associated constant `BackTrace::DISABLED`? Backtrace::disabled() is for constructing a backtrace whose...

Oh, my bad.

Now that Error::backtrace has been removed, this is effectively a full stabilization!

I filed a radar and put this in "description": > I use/depend on a plugin called Polychromatic (https://github.com/kolinkrewinkel/Polychromatic) that highlights each variable a different color. Since Xcode plugins no longer...