-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
promot debug_assert to assert #94712
promot debug_assert to assert #94712
Conversation
(rust-highfive has picked a reviewer for you, use r? to override) |
@bors r+ rollup |
📌 Commit 776be7e has been approved by |
…sumption, r=Mark-Simulacrum promot debug_assert to assert Fixes rust-lang#94705
I guess the question is if that is the only case in libstd where we made this assumption (about POSIX error lists being exhaustive)? It was just the first one I found, that's why it ended up in the issue. |
…sumption, r=Mark-Simulacrum promot debug_assert to assert Fixes rust-lang#94705
I went by what @cuviper said about treating these on a case by case basis but maybe I misunderstood. I'd gladly take a look to see if there are more and create a PR? |
…askrgr Rollup of 8 pull requests Successful merges: - rust-lang#91993 (Tweak output for non-exhaustive `match` expression) - rust-lang#92385 (Add Result::{ok, err, and, or, unwrap_or} as const) - rust-lang#94559 (Remove argument from closure in thread::Scope::spawn.) - rust-lang#94580 (Emit `unused_attributes` if a level attr only has a reason) - rust-lang#94586 (Generalize `get_nullable_type` to allow types where null is all-ones.) - rust-lang#94708 (diagnostics: only talk about `Cargo.toml` if running under Cargo) - rust-lang#94712 (promot debug_assert to assert) - rust-lang#94726 (:arrow_up: rust-analyzer) Failed merges: r? `@ghost` `@rustbot` modify labels: rollup
Fixes #94705