You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Awesome. I’m looking forward to seeing how you fix it. I was digging around a bit, but wasn’t able to figure it out before I had to leave for work this morning.
Brent Michalski
Senior iOS Engineer
Brent.Michalski@gmail.com
636-373-1015
On Mar 27, 2019, 8:12 AM -0500, Anton Plebanovich ***@***.***>, wrote:
Thanks for report. I'm on it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
The Sequence protocol no longer has a SubSequence associated type. Methods on Sequence that previously returned SubSequence now return concrete types. For example, suffix(_:) now returns an Array. (45761817)
On Mar 27, 2019, at 10:18 AM, Anton Plebanovich ***@***.***> wrote:
Version 4.0.0 was pushed. I was able to compile with Swift 5.0.0 and Xcode 10.2
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.
Activity
anton-plebanovich commentedon Mar 27, 2019
Thanks for report. I'm on it.
perlguy99 commentedon Mar 27, 2019
anton-plebanovich commentedon Mar 27, 2019
@perlguy99 With Swift 5.0
.dropFirst()operator now returns different tupe.https://developer.apple.com/documentation/xcode_release_notes/xcode_10_2_release_notes/swift_5_release_notes_for_xcode_10_2
anton-plebanovich commentedon Mar 27, 2019
Version
4.0.0was pushed. I was able to compile with Swift 5.0.0 and Xcode 10.2perlguy99 commentedon Mar 27, 2019