It wasn’t changed, it has *always* been C++14 since the day we open sourced it. 
I only investigated the platforms we officially support (Ubuntu 14.04/15.10 at 
the time, and macOS 10.10+ IIRC).

 - Daniel

> On Dec 19, 2017, at 2:21 PM, Ted Kremenek <kreme...@apple.com> wrote:
> 
> Daniel,
> 
> When you changed llbuild to require C++14, what platforms did you take into 
> account with that change?  If you have already done the assessment here it 
> could speed a resolution of a decision.
> 
> Thanks,
> Ted
> 
>> On Dec 13, 2017, at 3:19 PM, Daniel Dunbar via swift-lldb-dev 
>> <swift-lldb-...@swift.org> wrote:
>> 
>> FWIW, llbuild requires C++14.
>> 
>> We have to do some minor shenanigans to workaround bugs in libstdc++ on 
>> 14.04, and our use is probably minimal, but just throwing that out there.
>> 
>> - Daniel
>> 
>>> On Dec 13, 2017, at 1:45 PM, Jordan Rose via swift-lldb-dev 
>>> <swift-lldb-...@swift.org> wrote:
>>> 
>>> No one else has commented on this yet today, so I'll put in that I don't 
>>> have any objections to this and don't foresee any major problems. The one 
>>> place where we'd need to be careful is with LLDB, which imports Swift 
>>> headers; if Swift is going to move to C++14, then Swift-LLDB probably has 
>>> to as well. LLDB folks, what do you think?
>>> 
>>> The other thing to check is if our minimum Clang or libstdc++ requirements 
>>> on Linux didn't support C++14. It looks like our README is vague on that, 
>>> but LLDB already suggests a minimum requirement of Clang 3.5, which is new 
>>> enough. I suspect we're okay here.
>>> 
>>> Jordan
>>> 
>>> 
>>>> On Dec 13, 2017, at 10:36, Saleem Abdulrasool via swift-dev 
>>>> <swift-dev@swift.org> wrote:
>>>> 
>>>> Hi,
>>>> 
>>>> The newer Windows SDK requires the use of C++14 (the SDK headers use 
>>>> `auto` return types without trailing type information).  Joe mentioned 
>>>> that there was some interest in switching the rest of swift to C++14 as 
>>>> well.  I figured that I would just start a thread here to determine if 
>>>> this is okay to do globally rather than just specifically for the Windows 
>>>> builds to ensure that we can build the Windows components.
>>>> 
>>>> Thanks.
>>>> 
>>>> -- 
>>>> Saleem Abdulrasool
>>>> compnerd (at) compnerd (dot) org
>>>> _______________________________________________
>>>> swift-dev mailing list
>>>> swift-dev@swift.org
>>>> https://lists.swift.org/mailman/listinfo/swift-dev
>>> 
>>> _______________________________________________
>>> swift-lldb-dev mailing list
>>> swift-lldb-...@swift.org
>>> https://lists.swift.org/mailman/listinfo/swift-lldb-dev
>> 
>> _______________________________________________
>> swift-lldb-dev mailing list
>> swift-lldb-...@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-lldb-dev
> 

_______________________________________________
swift-dev mailing list
swift-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-dev

Reply via email to