Thanks everyone for the insightful review discussion! The Language Workgroup talked about this proposal and the review feedback, and arrived at the following conclusions:
- The SwiftPM manifest API based on
SwiftSetting
rather than the target is a better design. This offers more control over when to enable the features, andSwiftSetting
already represents build settings specific to Swift. - The term "upcoming feature" is less confusing than "future feature". During our verbal discussion, it became abundantly clear that "future feature" is hard to pronounce! We agree that it's best to avoid two consecutive words that are so similar, and "upcoming" is just as clear as "future".
- The short-circuiting of parsing call syntax should apply to both
||
and&&
.
The author has updated the proposal to incorporate these changes, and the review has been extended through July 11th to gather more discussion on the above modifications. The proposal has also incorporated explanations of Swift language version and Swift tools version, and how these two concepts interact.
These points have received some discussion already, so we'll continue the extended review in this thread.
Thank you,
Holly Borla
Review Manager