-
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 RwLock
to mc-sgx-tstdc
#260
Conversation
Current dependencies on/for this PR:
This comment was auto-generated by Graphite. |
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 #260 +/- ##
=======================================
Coverage 90.30% 90.30%
=======================================
Files 45 45
Lines 3949 3949
=======================================
Hits 3566 3566
Misses 383 383 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
11ca0e6
to
a9d62a9
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.
LGTM, but with the same suggestion as on Mutex
: recommend Result<bool, Error>
for try_lock()
-esque calls that can simply not grab the lock vs. fail for other reasons.
018f2da
to
79a007e
Compare
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.
79a007e
to
599094d
Compare
✅ This pull request merged successfully as part of a Graphite job |
No description provided.