-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support XCode 9+ #23
Comments
Thanks for the issue writeup. This is really a swift 4.0 -> 4.1 issue, but it was forced by the Xcode 9.3 update. We're generally committed to supporting the latest non-beta releases of Xcode and Swift. So, we can't just switch back to flatMap as that means we would not compile for Swift 4.1. We could either:
Hope this helps. |
I'd guess within a day. if that doesn't happen, ping us/me in this ticket. Also, you'll have to agree to the Comcast CLA before we could merge. I'm showing that you have not signed. Let me know if you have technical problems with that. |
I did submit my agreement but it seems to not update. Getting a message saying it might be my email but I verified my email used for the commit is under my profile. |
Yeah, I'm not sure either. I will check with our open source GitHub admins and get back to you. |
Seems it was just updated. CLA signed. |
Fixed and merged. |
@jgainfort mamba 1.0.5 is released. Cocoapods takes a little time if that's what you're using. |
@dcoufal Thank you! |
Hi! The README states that the library supports XCode 9+ but is using an operator requiring XCode 9.3+.
Seems this was introduced with this commit and changing flatMap to compactMap
2ecd85c
Is the intention still to support XCode 9+ or to move to only supporting 9.3+? Would a PR converting compactMap back to flatMap be acceptable?
The text was updated successfully, but these errors were encountered: