Repository navigation
None unification #1278
Description
Activity
Marked as needs discussion since it would be good to understand the consequences more precisely.
- added this to the milestone
on Apr 8, 2016 - removed this from the milestone
on Mar 29, 2017 There is no more
Void, andNonealways meansNoneTyp()so I think this can be closed.
Currently,
Nonetypes in the code either mean:Voidtype: a type that cannot be usedNone: an uninhabited type (i.e. a type without any values)NoneTyptype: the type that contains only the valueNone(this cannot currently be explicitly specified)After doing proper Optional checking, I propose that we make
Nonetypes always meanNoneTyp. Optional checking will prevent functions that returnNonefrom being used in places they shouldn't, and allowing users to specify something is the uninhabited type isn't currently useful at all.