Remove the spurious dependency on AsyncKit #634
Merged
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.
These changes are now available in 1.52.0
Although each of the Fluent database drivers depends on
AsyncKitfor (poor) connection pooling,FluentKititself does not need any ofAsyncKit's services. It was only being used for some simpleEventLoopFutureutilities, and wasn't even being reexported (thankfully). This removes the completely unnecessary dependency altogether.Additional changes:
MemberImportVisibility-correctMirrorBypasslogic is now enabled in Swift 6.1