Open lacasseio opened 5 years ago
We already have #397 and #367 and added source compatibility to Swift components in 4.6 -- is this for something else?
The context of this issue was around Swift 5. The question is do we want to catch up with the Swift release or do we want to provide a way for users to extend Gradle and provide the required model element and compile flags?
Several ways this can happen. Either 1) we add source compatibility as a first class citizen or 2) we allow for extensibility to add custom source compatibility, resolution and compiler flag transform.
At the moment, option 1 is probably more viable and easier to do as the tool chain selector is not made extensible publically.