Move foundation extensions behind traits #81
Draft
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.
Motivation
Currently this package extends various Foundation types in a separate module. One problem with this module is that it unconditionally imports
FoundationNetworking
. This is undesirable on Linux since it bringscurl
as a dependency. Additionally, the discoverability of having to import an additional module isn't great.Modification
This PR introduces two new traits that enable extensions on types from
FoundationEssentials
andFoundationNetworking
respectively. Giving adopters fine control of what they want to link against. It also moves all the extensions into the mainHTTPTypes
module.Result
Only a single module that is configurable through package traits.