-
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
UnwindSafe and RefUnwindSafe should be in libcore #64086
Labels
C-feature-request
Category: A feature request, i.e: not implemented / a PR.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
Comments
Mark-Simulacrum
added
C-feature-request
Category: A feature request, i.e: not implemented / a PR.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
labels
Sep 2, 2019
FWIW I also needed |
I run into this when changing an use std::panic::RefUnwindSafe;
use std::sync::Mutex as StdMutex;
use parking_lot::Mutex as ParkingLotMutex;
fn assert_ref_unwind_safe<T: RefUnwindSafe>(t: T) {
}
fn main() {
assert_ref_unwind_safe(StdMutex::new(0));
assert_ref_unwind_safe(ParkingLotMutex::new(0));
} Errors:
But |
Triage: no change |
I believe this was implemented in #84662 and shipped with rustc 1.56, so this can be closed now |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-feature-request
Category: A feature request, i.e: not implemented / a PR.
T-libs-api
Relevant to the library API team, which will review and decide on the PR/issue.
I think that would be useful to allow pure no_std libraries to implement those traits without needing the
std
cargo feature.cc @gnzlbg, you've asked about this #40628.
The text was updated successfully, but these errors were encountered: