Fix new NIO warnings #300
Merged
Fix new NIO warnings #300
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
@@ Coverage Diff @@
## main #300 +/- ##
=======================================
Coverage 43.91% 43.91%
=======================================
Files 115 115
Lines 9680 9680
=======================================
Hits 4251 4251
Misses 5429 5429
Flags with carried forward coverage won't be shown. Click here to find out more.
|
fabianfett
force-pushed
the
ff-fix-new-nio-warnings
branch
from
b73c4b6 to
60aa4db
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR brings us up to speed with current Swift NIO main branch and fixes the warnings that will show up once a new NIO release is cut.