> On 7 févr. 2017, at 21:57, Slava Pestov wrote:
>
>>
>> On Feb 7, 2017, at 8:14 PM, Guillaume Lessard via swift-users
>> wrote:
>>
>> I keep running into weird things with Swift 3 Collections.
>>
>> A) Collection has its count property defined as an Int via IndexDistance:
>>
>> public pro
Saagar Jha
> On Feb 6, 2017, at 10:57 PM, Andrew Trick wrote:
>
>
>> On Feb 6, 2017, at 8:51 PM, Dave Abrahams wrote:
>>
>>
>> on Mon Feb 06 2017, Andrew Trick wrote:
>>
>>> Is a missing declaration a use case that needs to be supported?
>>
>> I couldn't say.
>>
>>> Wouldn’t it be more
> On Feb 7, 2017, at 8:14 PM, Guillaume Lessard via swift-users
> wrote:
>
> I keep running into weird things with Swift 3 Collections.
>
> A) Collection has its count property defined as an Int via IndexDistance:
>
> public protocol Collection : Indexable, Sequence {
>associatedtype Inde
I keep running into weird things with Swift 3 Collections.
A) Collection has its count property defined as an Int via IndexDistance:
public protocol Collection : Indexable, Sequence {
associatedtype IndexDistance : SignedInteger = Int // line 182 in
Collection.swift
public var count: In
> On Feb 7, 2017, at 4:58 PM, Chengyin Liu wrote:
>
> Thanks for the feedback!
>
> > This is probably source-compatibility that you want, not necessarily ABI
> > compatibility.
>
> You are right. Thank you for the correction.
>
> > BTW, are you mixed-source? If so, were you able to try out
Thanks for the feedback!
> This is probably source-compatibility that you want, not necessarily ABI
compatibility.
You are right. Thank you for the correction.
> BTW, are you mixed-source? If so, were you able to try out PCH for
bridging headers as identified here: https://swift.org/blog/bridgin
on Mon Feb 06 2017, Andrew Trick wrote:
>> On Feb 6, 2017, at 8:51 PM, Dave Abrahams wrote:
>>
>>
>> on Mon Feb 06 2017, Andrew Trick wrote:
>>
>
>>> Is a missing declaration a use case that needs to be supported?
>>
>> I couldn't say.
>>
>>> Wouldn’t it be more proper to use selector bas
Comments:
> Since the Swift ABI changed between versions 2 and 3, even correct Swift 3
> code that imports Swift 2 libraries will not compile. This incompatibility
> made it difficult to parallelize code conversion.
This is probably source-compatibility that you want, not necessarily ABI
compa
Hi all,
At Airbnb we recently migrated to Swift 3, just in time for Xcode 8.3. We
waited as long as possible because our codebase is massive. We have
hundreds thousands lines of Swift.
In the end we were able to migrate without a code freeze. 3 engineers
worked on it for 3 weeks without disruptin
HI!
Its an actually Swift version of swiftenv(https://github.com/kylef/swiftenv).
It now can install multiple versions and have the basic facilities of a
version manager. Though it is not complete and there are many to improve
but worth a try. It only works on Linux for now. It was a project to lea
10 matches
Mail list logo