Add deconstruct to Option/Maybe to support eg (hasValue, value) = collection.TryFirst(...) about succinct HOT 6 CLOSED

Option<T>.ValueOrDefault seems legit.

from succinct.

What will value contain if hasValue is false?

from succinct.

default(T) would seem the obvious choice. I'd prefer the idea that its undefined, but out parameters have to be set, always, so that isn't an option.

If you think this inherently a bad idea though, I'm open to being convinced to drop it.

from succinct.

I don't think that's a bad idea, but I feel like it should be consistent with how Option<T>.Value behaves. Right now it's determined to throw an exception if HasValue == false, so maybe Option<T>.Value should return default(T) as well in this case.

from succinct.

If I changed Option<T>.Value to return default<T> when there's no value, then that would be a breaking change. So the choices are:

1. Wait until v4 and introduce that breaking change (in reality there need not be a wait, v4 could be the next release, though this would mean creating a major version release though for a minor feature).
2. Add a Option<T>.ValueOrDefault property that behaves this way and leave Option<T>.Value, as is.

from succinct.

Added to v3.1

from succinct.