-
Notifications
You must be signed in to change notification settings - Fork 10.2k
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
Avoid using generic static members on Duration across module boundaries #73419
Merged
stephentyrone
merged 3 commits into
apple:main
from
stephentyrone:duration-initializers-without-generics
May 4, 2024
Merged
Avoid using generic static members on Duration across module boundaries #73419
stephentyrone
merged 3 commits into
apple:main
from
stephentyrone:duration-initializers-without-generics
May 4, 2024
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Because the clocks are implemented in Concurrency, but Duration is in the Swift module, these don't get specialized. Add a fully-concrete internal init in Concurrency to avoid the problem.
phausler
approved these changes
May 3, 2024
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
lorentey
approved these changes
May 3, 2024
@swift-ci test |
@swift-ci test |
gottesmm
pushed a commit
to gottesmm/swift
that referenced
this pull request
May 6, 2024
…es (apple#73419) * Avoid using generic static members on Duration across module boundaries Because the clocks are implemented in Concurrency, but Duration is in the Swift module, these don't get specialized. Add a fully-concrete internal init in Concurrency to avoid the problem. * Call self.init(_high:low:) explicitly. * Add availability annotation. (cherry picked from commit da9922d)
stephentyrone
added a commit
that referenced
this pull request
May 11, 2024
* Make static [milli/micro/nano]seconds members on Duration inlinable (#73429) This means that they can't use _Int128 for their implementation, but efficient implementation of these using only 64b arithmetic is pretty straightforward, so that's OK. This allows them to be specialized and mostly optimized away in release builds. * Avoid using generic static members on Duration across module boundaries (#73419) * Avoid using generic static members on Duration across module boundaries Because the clocks are implemented in Concurrency, but Duration is in the Swift module, these don't get specialized. Add a fully-concrete internal init in Concurrency to avoid the problem. * Call self.init(_high:low:) explicitly. * Add availability annotation.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Because the clocks are implemented in Concurrency, but Duration is in the Swift module, these don't get specialized. Add a fully-concrete internal init in Concurrency to avoid the problem.