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

Remove @available annotation from async APIs. #98

Merged
merged 2 commits into from
Nov 3, 2021

Conversation

tachyonics
Copy link
Contributor

@tachyonics tachyonics commented Nov 3, 2021

Issue #, if available:

Description of changes:

  1. Remove @available annotation from async APIs, increase the requirement for non Linux platforms to the upcoming 5.5.2 (which will backport async support to the earlier Apple OSs).
  2. Remove Swift 5.2 from CI checks as it has dropped out of its support window.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@tachyonics tachyonics merged commit cc2ca1f into main Nov 3, 2021
@tachyonics tachyonics deleted the remove_available_annotation_for_async branch November 3, 2021 19:02
Lukasa added a commit to Lukasa/smoke-http that referenced this pull request Oct 25, 2024
In amzn#98, @tachyonics added a vendored copy of a NIO method on
EventLoopFuture to avoid needing to add availability guards. I don't
think that should have been necessary then, but it certainly isn't now,
as smoke-http's minimum deployment targets match the extension in NIO.

This extension contravened one of NIO's requirements on its dependencies:
https://github.com/apple/swift-nio/blob/main/docs/public-api.md#4-extending-nio-types.
Ideally when it was added, it should have been given a different name.

This extension has been working, but it is now conflicting with NIO's main on
Swift 5.9. This patch removes the now-vestigial extension, as it isn't needed.
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