Skip to content
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

Removing Result in favor of Swift.Result #702

Merged
merged 12 commits into from
Apr 5, 2019
Merged

Removing Result in favor of Swift.Result #702

merged 12 commits into from
Apr 5, 2019

Conversation

NachoSoto
Copy link
Member

@NachoSoto NachoSoto commented Jan 15, 2019

I got out of my cockpit for a day to do some coding and experiment with this.

I understand we'd be dropping support for anything prior to Swift 5.0, so this is kinda just a proof of concept until the next major version?

Code is almost compiling, I'll try to finish it tomorrow.

Checklist

  • Update Quick and Nimble.
  • Fix tests.
  • Updated CHANGELOG.md.
  • Update Package.resolved (not sure how)
  • Deprecation for NoError (with Never fixit)

@ikesyo
Copy link
Member

ikesyo commented Jan 15, 2019

Ref: #696

@andersio
Copy link
Member

@mdiep Do we not want to keep NoError as a typealias?

@mdiep
Copy link
Contributor

mdiep commented Mar 14, 2019

That's not a bad idea. Maybe a deprecated typealias? That would ease migration.

@NachoSoto
Copy link
Member Author

This is 90% I think. If anyone wants to finish this please go ahead 🙏

@NachoSoto
Copy link
Member Author

That's not a bad idea. Maybe a deprecated typealias? That would ease migration.

Done!

@mdiep mdiep changed the title [WIP] Removing Result in favor of Swift.Result Removing Result in favor of Swift.Result Mar 31, 2019
@mdiep
Copy link
Contributor

mdiep commented Mar 31, 2019

I think this is ready, but I'd like to get a 5.0.1 release in first to fix the warnings in Xcode 10.2.

@@ -22,16 +21,16 @@ internal extension SignalProducer {
/// Halts if an error is emitted in the receiver signal.
/// This is useful in tests to be able to just use `startWithNext`
/// in cases where we know that an error won't be emitted.
func assumeNoErrors() -> SignalProducer<Value, NoError> {
return self.lift { $0.assumeNoErrors() }
func assumeNevers() -> SignalProducer<Value, Never> {
Copy link
Member

@andersio andersio Mar 31, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should not be renamed since the real meaning is now lost.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. The "no error" part of this method name was beyond the NoError type.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done. 👍

@mdiep mdiep requested a review from andersio April 5, 2019 12:38
@andersio andersio merged commit 5314acc into master Apr 5, 2019
@andersio andersio deleted the remove-result branch April 5, 2019 20:03
@iv-mexx iv-mexx mentioned this pull request Apr 10, 2019
1 task
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants