-
-
Notifications
You must be signed in to change notification settings - Fork 53
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 Sendable conformance #110
Conversation
Codecov Report
@@ Coverage Diff @@
## main #110 +/- ##
==========================================
- Coverage 78.13% 77.91% -0.22%
==========================================
Files 72 72
Lines 3060 3075 +15
==========================================
+ Hits 2391 2396 +5
- Misses 669 679 +10
Continue to review full report at Codecov.
|
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.
Hmmm I guess that looks good. We may keep updating how we adopt Sendable but since your types here are properly just fine it looks good. Confirming that NIO types I guess you'll be able to undo once NIO does so itself - I don't actually know what the game plan here is, will need to think or better yet ask Becca about it - there is a proposal on the forums about adopting Sendable now
too old |
Add
Sendable
conformance to Hummingbird types.Much of this means setting
@unchecked Sendable
on types inherited from NIOThere are also a couple of places where I have added
@unchecked Sendable
on my own types because I don't have a solution yet to ensuring they areSendable
. ieHBEndpointResponder
where it needs to be mutable when routes are being added but post that is static. I can write code to get around this.HBRequest.ResponsePatch
which is a reference object that is editable from route.Requiring
Sendable
is a really good way to find all your possible race conditions