Skip to content
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

6.0: [BitwiseCopyable] Promote to feature. #73282

Conversation

nate-chandler
Copy link
Contributor

@nate-chandler nate-chandler commented Apr 26, 2024

Explanation: SE-0426 has been accepted.

Change the spelling to BitwiseCopyable. Maintain a _BitwiseCopyable protocol for source compatibility with early adopters.

Promote the BitwiseCopyable and ConformanceSuppression features to language features. Remove gating from functions added by the proposal. Add deprecations for functions deprecated in the proposal.

Scope: Affects users of BitwiseCopyable.
Issue:rdar://127521923
Original PR: #73235
Risk: Low.
Testing: CI testing.
Reviewer: Andrew Trick ( @atrick )

The ability to suppress conformance to BitwiseCopyable was part of the
accepted SE-428.
The unconstrained overloads of loadUnaligned and storeBytes were
deprecated in SE-0426.
@nate-chandler nate-chandler force-pushed the cherrypick/release/6.0/bitwise-copyable/enable branch from a759d7c to a8e8ab0 Compare April 26, 2024 15:05
@nate-chandler
Copy link
Contributor Author

@swift-ci please test

@nate-chandler nate-chandler marked this pull request as ready for review May 4, 2024 00:57
@nate-chandler nate-chandler requested a review from a team as a code owner May 4, 2024 00:57
@nate-chandler nate-chandler requested a review from tbkka May 4, 2024 20:14
@nate-chandler nate-chandler merged commit 6135791 into apple:release/6.0 May 6, 2024
5 checks passed
@nate-chandler nate-chandler deleted the cherrypick/release/6.0/bitwise-copyable/enable branch May 6, 2024 15:40
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.

None yet

2 participants