Add CasePathsCore module
#212
Merged
Conversation
This file contains 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
It's possible for a library to integrate with case paths in a way that doesn't require their use and the penalty involved in building their macros, so let's introduce a "core" module that contains the core functionality of the library, less macros and other deprecations.
mbrandonw
approved these changes
Jan 13, 2025
|
To build combined documentation: |
mbrandonw
approved these changes
Jan 16, 2025
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.
The
@CasePathablemacro requires SwiftSyntax, which is quite heavy to rely on and build, but not every library or app depending on case paths needs to build or load the macro, so let's extract the core functionality of case paths to a "core" module that can be built and linked against in isolation.