Add value property to Result

[Ben_Cohen]

@DevAndArtist

I kindly remind the thread of the debacle behind toggle() and the rejection of isFalse on Bool .

I don't think "debacle" is an appropriate characterization of the toggle review. The core team was clear on the merit of that proposal when accepting it. In fact that was where we codified the criteria for this kind of addition.

@bzamayo gives the right answer here:

@bzamayo

If throwing accessors existed when Result was formalised, we would have done it then.

The value of a result or a task is very much a property of the type, not a function that requires execution, insomuch as anything deserves to be a property (it doesn't even require awaiting unlike on Task – it's right there for the taking), and had throwing properties existed this is what it would have been called originally.

This is what distinguishes it from isFalse, which is not the "if we had our time again" alternative to !.

@bzamayo

It'd be nice if the code documentation for get() could be updated to say something like 'Prefer value spelling'.

This is a good idea – essentially the softest of deprecations. I'll add to the proposal.