> On Dec 13, 2017, at 2:30 PM, Jordan Rose wrote:
>
>
>
>> On Dec 13, 2017, at 14:19, Saleem Abdulrasool wrote:
>>
>>> On Dec 13, 2017, at 1:45 PM, Jordan Rose 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'
> On Dec 13, 2017, at 14:19, Saleem Abdulrasool wrote:
>
>> On Dec 13, 2017, at 1:45 PM, Jordan Rose 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
> On Dec 13, 2017, at 1:45 PM, Jordan Rose 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
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
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 oka
