[swift-lldb-dev] [swift-dev] Switching swift to C++14

[Jordan Rose]

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 at 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 at swift.org
> https://lists.swift.org/mailman/listinfo/swift-dev