Skip to content

[Release Note] Swift 5.10 closes all known holes in compile-time strict concurrency checking. #71080

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

Merged
merged 3 commits into from
Jan 23, 2024

Conversation

hborla
Copy link
Member

@hborla hborla commented Jan 23, 2024

Add a release note for Swift 5.10 closing all known holes in the static data-race safety model under -strict-concurrency=complete.

This change also makes minor editorial changes to improve the release notes for SE-0411 and SE-0412.

@hborla hborla changed the title [Concurrency] Add a 5.10 release note for closing all known holes in the static data-race safety programming model. [Release Note] Swift 5.10 closes all known holes in compile-time strict concurrency checking. Jan 23, 2024
@hborla hborla force-pushed the data-race-safety-changelog branch 2 times, most recently from 2f42bb7 to 2ea5391 Compare January 23, 2024 04:54
@hborla hborla force-pushed the data-race-safety-changelog branch from 2ea5391 to fa740bc Compare January 23, 2024 04:57
@hborla
Copy link
Member Author

hborla commented Jan 23, 2024

@swift-ci please smoke test

@slavapestov
Copy link
Contributor

But do you have a proof that no unknown holes exist? :-)

@hborla
Copy link
Member Author

hborla commented Jan 23, 2024

But do you have a proof that no unknown holes exist? :-)

Of course not, but this is still an important milestone 🙂 and more importantly, now the community knows that if they do find another data-race safety hole, they should report it because I don't know about it!

@hborla hborla merged commit da628e3 into swiftlang:main Jan 23, 2024
@hborla hborla deleted the data-race-safety-changelog branch January 23, 2024 16:51
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.

2 participants