Skip to content

Remove the last remaining NIOAtomic #607

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 2 commits into from
Aug 3, 2022

Conversation

Lukasa
Copy link
Collaborator

@Lukasa Lukasa commented Aug 3, 2022

Motivation

Warnings aren't great, and NIOAtomic is deprecated.

Modifications

Replace the last use of NIOAtomic with ManagedAtomic.

Result

Fewer warnings
Fixes #606

Motivation

Warnings aren't great, and NIOAtomic is deprecated.

Modifications

Replace the last use of NIOAtomic with ManagedAtomic.

Result

Fewer warnings
Fixes swift-server#606
@Lukasa Lukasa added the 🔨 semver/patch No public API change. label Aug 3, 2022
@Lukasa Lukasa requested a review from dnadoba August 3, 2022 08:29
@adam-fowler
Copy link
Member

One minor thing, maybe the version constraints in Package.swift should require versions that don't use NIOAtomics

@Lukasa
Copy link
Collaborator Author

Lukasa commented Aug 3, 2022

Do you mean versions of swift-nio? I don't think that's necessary: there are no relevant correctness issues with old copies of NIO, and we don't require the new ones, so there's no particular issue with letting users resolve older versions if that's necessary to get a buildable tree.

@Lukasa Lukasa merged commit 0527bbb into swift-server:main Aug 3, 2022
@Lukasa Lukasa deleted the cb-change-atomics branch August 3, 2022 09:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🔨 semver/patch No public API change.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

HTTPClient is still using NIOAtomic
3 participants