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

I've filed https://bugs.swift.org/browse/SR-2582 for this. On Tue, Sep 6, 2016 at 10:37 AM, Jordan Rose wrote: > > On Jul 29, 2016, at 21:13, Chris Lattner via swift-dev < > swift-dev@swift.org> wrote: > > > On Jul 29, 2016, at 5:55 PM, Jacob Bandes-Storch > wrote: > > Here are a few thoughts:

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

> On Jul 29, 2016, at 21:13, Chris Lattner via swift-dev > wrote: > > >> 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

Re: [swift-dev] [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, while still keeping the old func

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

Importing the right version of a module (such as the standard library) when more than one are available is just a search-paths problem. Supporting multiple versions of the language's syntax and ABI, though, as far as I can tell, requires the switch to be deeply baked into the compiler. So I don't

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

> On Aug 3, 2016, at 1:16 AM, Brent Royal-Gordon via swift-dev > wrote: > >> 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" syn

Re: [swift-dev] [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 interesting questions: * Do

Re: [swift-dev] [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. -Chris > -language-ve

Re: [swift-dev] [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: > > On Jul 29, 2016, at

Re: [swift-dev] [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 to conditionally enable lar