search

APUtils / KeyboardAvoidingView

Simple solution for keyboard avoiding. View that manages it's bottom constraint constant or frame height to avoid keyboard
MIT License
23 stars 6 forks source link

Error in UIView+Utils.swift #2

Open perlguy99 opened 5 years ago

perlguy99 commented 5 years ago

With Xcode 10.2, I am getting the following error when trying to build...

Cannot convert return expression of type 'DropFirstSequence<UnfoldSequence<UIView, (UIView?, Bool)>>' to return type 'AnySequence<UIView>'

This is happening on line 14 of Extensions.swift

anton-plebanovich commented 5 years ago

Thanks for report. I'm on it.

perlguy99 commented 5 years ago

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 notifications@github.com, 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.

anton-plebanovich commented 5 years ago

@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

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)

anton-plebanovich commented 5 years ago

Version 4.0.0 was pushed. I was able to compile with Swift 5.0.0 and Xcode 10.2

perlguy99 commented 5 years ago

Ugh, how annoying!

Thanks for looking into this!

Sent from my iPad

On Mar 27, 2019, at 10:18 AM, Anton Plebanovich notifications@github.com 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.