You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think it will be useful to have none from maybe singleton, to allow direct comparison two values - and because obviously different nones should be equal.
It might be a breaking change, of course .
The text was updated successfully, but these errors were encountered:
I think having a function for one value and a field for another is not a good idea. The API in this case will be slightly inconsistent. But, I'm open to discussing it, why do you think it would be better to have the none field?
I think it will be useful to have
none
from maybe singleton, to allow direct comparison two values - and because obviously differentnone
s should be equal.It might be a breaking change, of course .
The text was updated successfully, but these errors were encountered: