-
Notifications
You must be signed in to change notification settings - Fork 10
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
Add the mc-sgx-tstdc
crate
#256
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
3c9aa94
to
8a0737e
Compare
54b309c
to
12c88f9
Compare
8a519a2
to
6f8b055
Compare
8679d1e
to
a4b636f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me.
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #256 +/- ##
=======================================
Coverage 90.27% 90.27%
=======================================
Files 45 45
Lines 3950 3950
=======================================
Hits 3566 3566
Misses 384 384 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Previously `try_lock()` would return `Ok(())` or `Err(Error)`. This resulted in `Error::Busy` coming back in `Err()` when another thread had the lock. Another thread owning the lock in a `try_lock()` call is expected behavior and isn't a traditional _error_. Now `try_lock()` returns a `bool` in normal expected operation to indicate if the lock was acquired or not.
900f7ab
to
53886fa
Compare
✅ This pull request merged successfully as part of a Graphite job |
Add
Mutex
primitive