-
Notifications
You must be signed in to change notification settings - Fork 744
remove Send + Sync not needed from client session storage field #2087
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
remove Send + Sync not needed from client session storage field #2087
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #2087 +/- ##
=======================================
Coverage 94.78% 94.78%
=======================================
Files 102 102
Lines 23497 23497
=======================================
Hits 22271 22271
Misses 1226 1226 ☔ View full report in Codecov by Sentry. |
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.
Since we don't have these bounds on any of the other Arc<dyn>
s in the ServerConfig
(or ClientConfig
), I suppose this is fine.
Benchmark resultsInstruction countsSignificant differencesClick to expand
Other differencesClick to expand
Wall-timeSignificant differencesClick to expand
Other differencesClick to expand
Additional informationCheckout details:
|
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.
Thanks!
(I missed it initially, but this is good because StoresServerSessions
already has Send + Sync
as trait bounds. That should be a clippy lint!)
While working on a proposal to support using
alloc::rc::Rc
, as discussed as a possible solution for #2068, I discovered a case of extraSend + Sync
that I think is not needed & one more thing that would need to be updated. Of course I could remove this as part of my proposal for #2068, but would rather keep this kind of cleanup in a separate proposal & commit if possible.FYI I did already get a green build of this proposal in my own fork.