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.

Sign up for GitHub

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

Jump to bottom

What's the purpose of having to, as, and compose? #6319

Closed
slisaasquatch opened this issue Nov 20, 2018 · 1 comment
Closed

What's the purpose of having to, as, and compose? #6319

slisaasquatch opened this issue Nov 20, 2018 · 1 comment
Labels
2.x Question

Comments

@slisaasquatch
Copy link
Contributor

From what I understand, to and as are exactly the same thing, minus the functional interface of course. compose is not the same, but where compose can be used, to or as can also be used (not the other way around).

So what's the reason behind these 3 methods? Is there any benefit of having all 3 of them instead of just 1?
@akarnokd
Copy link
Member

See #5729.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
2.x Question
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@akarnokd @slisaasquatch