Re: [swift-evolution] [Swift 4] Organizing source stability

> On Jul 29, 2016, at 5:20 PM, Jacob Bandes-Storch via swift-evolution > wrote: > > I am curious whether the team has thoughts on how to organize the compiler > codebase in such a way that new features can be added, and possibly > source-breaking changes made,

Re: [swift-evolution] [Swift 4] Organizing source stability

> On Jul 29, 2016, at 5:55 PM, Jacob Bandes-Storch via swift-evolution > wrote: > > • a top-of-file "shebang"-style comment indicating the version, > something like //#swift(4), mirroring the "#if swift" syntax `import Swift 3.1`? I think this brings up two

Re: [swift-evolution] [Swift 4] Organizing source stability

> On Jul 29, 2016, at 5:55 PM, Jacob Bandes-Storch wrote: > > Here are a few thoughts: > -swift=4 > -swift-version=4 -swift-version seems like the best option to me, but Jordan will have a strong opinion. I think he’s crazy busy with Swift 3 work until late next week.

Re: [swift-evolution] [Swift 4] Organizing source stability

Here are a few thoughts: - -swift=4 - -swift-version=4 - -language-version=4 - a top-of-file "shebang"-style comment indicating the version, something like //#swift(4), mirroring the "#if swift" syntax On Fri, Jul 29, 2016 at 5:27 PM, Chris Lattner wrote: >

Re: [swift-evolution] [Swift 4] Organizing source stability

> On Jul 29, 2016, at 5:20 PM, Jacob Bandes-Storch via swift-evolution > wrote: > > Chris writes: > - Source stability features: These should be relatively small, but important. > For example, we need a “-std=swift3” sort of compiler flag. We may also add > a way

[swift-evolution] [Swift 4] Organizing source stability

Chris writes: > - *Source stability features: *These should be relatively small, but > important. For example, we need a “-std=swift3” sort of compiler flag. We > may also add a way to conditionally enable larger efforts that are under > development but not yet stable - in order to make it