Introduce traits guarding dependencies that macros and -tool use #468
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 is a specific approach intended to remove the need to split the swift-java repository into more repositories.
The intended goal is to allow libraries to depend on swift-java WITHOUT having to depend on:
This design effectively means that a library just using the "no dependencies" pieces of swift-java would depend on it this way:
By "not enabling" the default traits, such library will NOT built swift-syntax and any of the other dependencies.
If another dependency, e.g. an application, also used SwiftJava and DID use the macros, these traits would become enabled -- as the developer intended -- however that is not a problem for the "middle" libraries, such as Skip which would not have to enable any of these traits nor care about the dependencies.
--
In addition to that, all dependencies of swift-java WILL promise to support Android shortly, as soon as we figure out some organizational things about them.