-
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
Create bindings for native mutexes #9105
Comments
@brson would this use pthreads or the uv_mutex stuff? |
Blocked by #9243, locks have the |
@cmr pthreads @alexcrichton I don't know that this needs to be blocked on that. Certainly LittleLock itself couldn't be initialized statically, but we could have a yet-more-primitive mutex that could still be initialized statically. Also, from a casual glance, LittleLock's destructor is just for deallocating the lock, which would not be necessary if we had the types defined in Rust. |
Here are some comments I left in IRC
|
Add `invalid_utf8_in_unchecked` changelog: Add [`invalid_utf8_in_unchecked`] closes: rust-lang#629 Don't know how useful of a lint this is, just saw this was a really old issue 😄.
The LittleLock type currently works by allocating a C++ lock_and_signal type. This makes it unsuitable for creating static mutexes. Create new bindings to the native mutex types, along with static initializers, port LittleLock, then delete lock_and_signal.
The text was updated successfully, but these errors were encountered: