Skip to content

[stdlib] fix an extraneous symbol exported by MutableSpan #81816

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

glessard
Copy link
Contributor

In #79650, one of the initializers was not marked @_alwaysEmitIntoClient, by mistake. This fixes the mistake, and adjusts the list of ABI symbols accordingly.

@glessard glessard requested a review from a team as a code owner May 28, 2025 20:36
@glessard
Copy link
Contributor Author

@swift-ci please build toolchain macOS platform

@glessard
Copy link
Contributor Author

@swift-ci please test

@glessard glessard requested a review from jmschonfeld May 28, 2025 21:38
@@ -55,8 +55,7 @@ extension MutableSpan: @unchecked Sendable where Element: Sendable {}
extension MutableSpan where Element: ~Copyable {

@unsafe
@_unsafeNonescapableResult
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just confirming: the removal of @_unsafeNonescapableResult was intentional?

Copy link
Contributor Author

@glessard glessard May 28, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes it's intentional: we don't need it given that a @lifetime annotation is in place. @_unsafeNonescapableResult predated the existence of the @lifetime annotation.

@glessard
Copy link
Contributor Author

@swift-ci please test macOS platform

@glessard
Copy link
Contributor Author

@swift-ci please test Windows platform

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants