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

Matcher functions should be optional in Optional.match #11

Open
fredvollmer opened this issue Apr 5, 2019 · 1 comment
Open

Matcher functions should be optional in Optional.match #11

fredvollmer opened this issue Apr 5, 2019 · 1 comment

Comments

@fredvollmer
Copy link

Is there any reason why both some and none have to specified in the object passed to the match function? Often times I only need to take action if the Option is defined, so I only want to pass some.
@yayoc
Copy link
Owner

yayoc commented Apr 6, 2019

There is no particular reason. Probably, We might be able to make both some and none properties optional.

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

No branches or pull requests
2 participants
@yayoc @fredvollmer