-
Notifications
You must be signed in to change notification settings - Fork 631
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 @preconcurrency
from internal EventLoopFuture
methods
#2135
Conversation
no longer needed because `@preconcurrency` is gone from the method definition.
@swift-nio-bot test perf please |
performance reportbuild id: 141 timestamp: Tue May 31 09:05:08 UTC 2022 results
comparison
significant differences found |
@swift-nio-bot test perf please |
performance reportbuild id: 142 timestamp: Tue May 31 09:10:48 UTC 2022 results
comparison
significant differences found |
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.
Nice, LGTM.
If we remove |
Motivation:
We want to remove
@preconcurrency
from our internal methods and fix the resulting sendable warnings/errors.Modifications:
@preconcurrency
from internal methods and remove code duplication that is no longer necessary.UnsafeMutableTransferBox
that can be used to make non-Sendable
valuesSendable
and mutable. It can be used to capture local mutable values in a@Sendable
closure and mutate them from within the closure.UnsafeMutableTransferBox
where we currently capture mutable variables from@Sendable
closures.Result:
All internal only uses of
@preconcurrency
are now gone. Less code duplication.