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

Deprecate -sequenceMany:, rename -sequenceNext: to -then: #635

Merged
merged 2 commits into from
Jul 2, 2013

Conversation

jspahrsummers
Copy link
Member

Fixes #624.

I noticed our +if:then:else: operator while implementing this, and I'm wondering if that might be confusing with -then:. However, they're used in pretty different contexts, and the parameter is of a different type in each case, so I could go either way.

@kastiglione
Copy link
Member

I can live with +if:then:else: and -then:.

I have one last idea: -relayTo:. I first thought of it in the relay race sense, but it also has the electrical signal connotation too.

@jspahrsummers
Copy link
Member Author

That's not a bad idea. It sounds pretty esoteric, but maybe that'll force people to read the documentation.

@ReactiveCocoa/reactivecocoa Any other input on the above?

@kastiglione
Copy link
Member

maybe that'll force people to read the documentation.

You forgot the :trollface:

@joshvera
Copy link
Member

joshvera commented Jul 1, 2013

✋ for -then:

@joshaber
Copy link
Member

joshaber commented Jul 2, 2013

I'd still lean towards -then: but I'm probably biased :trollface:

@jspahrsummers
Copy link
Member Author

🚢

@ghost ghost assigned joshaber Jul 2, 2013
@joshaber
Copy link
Member

joshaber commented Jul 2, 2013

💥

joshaber added a commit that referenced this pull request Jul 2, 2013
Deprecate -sequenceMany:, rename -sequenceNext: to -then:
@joshaber joshaber merged commit 082e3da into 2.0-development Jul 2, 2013
@joshaber joshaber deleted the deprecate-sequence-many branch July 2, 2013 16:49
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.

4 participants