> On Dec 13, 2017, at 2:30 PM, Jordan Rose <jordan_r...@apple.com> wrote: > > > >> On Dec 13, 2017, at 14:19, Saleem Abdulrasool <compn...@compnerd.org> wrote: >> >>> On Dec 13, 2017, at 1:45 PM, Jordan Rose <jordan_r...@apple.com> 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. >> >> The current Ubuntu LTS (16.04) has clang 4 which supports C++14. libstdc++ >> claims C++14 compliance in the 4.9 release. That is available in Xenial >> (16.04) as well. So, I believe that the dependency issue should not be a >> problem. > > We're talking minimal requirements, not current versions. Otherwise this > becomes a "should we drop support for X" thread, which is a different > proposition.
I was trying to clarify that the minimum requirements for C++14 would not be a problem with the current minimum system requirements for Linux. > Jordan
_______________________________________________ swift-dev mailing list swift-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-dev
