nim-lang / fusion

Fusion is for now an idea about how to grow Nim's ecosystem without the pain points of more traditional approaches.
MIT License
128 stars 16 forks source link

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

Open ringabout opened 3 years ago

ringabout commented 3 years ago

Ref https://github.com/nim-lang/Nim/pull/17147#issue-577813481

haxscramper commented 3 years ago

Discussed in https://github.com/timotheecour/Nim/issues/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?