-
Notifications
You must be signed in to change notification settings - Fork 12.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stabilizing panic_immediate_abort #115022
Comments
serde_derive is using the This is where the standard library is rebuilt instead of using the pre-built rlibs. It is unlikely that build-std is going to be stabilized any time soon but if you'd like to help out or track its progress then see https://github.com/rust-lang/wg-cargo-std-aware/issues |
That said, I would ask why you want it stabilized? There may be other designs that may achieve your goals. For example, I have previously discussed with some devs that I'd love a way to turn off std backtraces and that whole machinery. Perhaps a rustc flag like |
A way to override the panic handler while still using std, as one can override the global allocator, would be good enough for me. |
This can't be stabilized without also stabilizing rebuilding the standard library in the first place, which still has basic issues like trying to compile with |
Closing this as I think stabilizing build-std features are better tracked as part of that effort. Happy to reopen if people disagree. |
Is there an issue I can subscribe to for staying up to date with the stabilization effort? I was able to find that build-std is part of https://github.com/rust-lang/wg-cargo-std-aware, but I don’t see an issue about |
Forgive me if there's already a tracking issue for this, but I haven't been able to find one. I see that the build script for the precompiled serde_derive binary uses this feature (and thus a nightly toolchain), so there's clearly demand for it. How can we users help get it stabilized?
The text was updated successfully, but these errors were encountered: