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

fusion/matching should also use some and none instead of Some and None: #87

Open
ringabout opened this issue Apr 15, 2021 · 1 comment

Comments

@ringabout
Copy link
Member

Ref nim-lang/Nim#17147 (comment)

@haxscramper
Copy link
Contributor

Discussed in timotheecour/Nim#612. Some and None are chosen for similarity with kind prefix drop.

It would be trivial to implement some and none support too, but the intended way of writing would still be Some and None. (i.e. I can add check for "some", but don't want to switch whole documentation to new style). Is that acceptable?

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

No branches or pull requests

2 participants