-
Notifications
You must be signed in to change notification settings - Fork 13k
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
stabilize debug_non_exhaustive #83041
Conversation
r? @kennytm (rust-highfive has picked a reviewer for you, use r? to override) |
Co-authored-by: Yuki Okushi <[email protected]>
r? @m-ou-se |
I've started the FCP process on the tracking issue: #67364 (comment) Marking this as blocked. |
@bors r+ rollup |
📌 Commit b1fac3a has been approved by |
Rollup of 8 pull requests Successful merges: - rust-lang#83041 (stabilize debug_non_exhaustive) - rust-lang#83349 (Remove Option::{unwrap_none, expect_none}.) - rust-lang#83420 (Add documentation for rustdoc-gui tests) - rust-lang#83421 (Add Result::into_err where the Ok variant is the never type) - rust-lang#83427 (small cleanups in rustc_errors / emitter) - rust-lang#83434 (Update RELEASES.md) - rust-lang#83440 (Use intra-doc link in core::cell) - rust-lang#83442 (LLVMWrapper: attractive nuisance macros) Failed merges: - rust-lang#83438 (Update RELEASES.md) r? `@ghost` `@rustbot` modify labels: rollup
|
Do you want me to do some release notes? Do I just add them to RELEASES.md? |
@derekdreery IIRC you shouldn’t have to do anything; the |
tracking issue: #67364
but it is still an open question whether the other
Debug*
struct's should have a similar method. I would guess that would best be put underneath a new feature gate, as this one seems uncontroversial enough to stabilize as is