Replies: 2 comments 1 reply
-
The status is... in transition.
The documentation will be updated when |
Beta Was this translation helpful? Give feedback.
0 replies
-
@JalonSolov Thanks. I'm assuming my summary was correct and from now on should code accordingly. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
On 11-Jul-2022 @medvednikov commented:
This seems to contradicted by the current documentation, which I'm guessing is out of date:
The same documentation also states:
There is also this RFC, updated 21-Apr-2022: Redesign of error and none handling but it's implementation status is unclear (to me).
From what I can tell things as they currently stand can be sumarised as follows:
!T
returns aResult
type and should be used if you want to return a value or an error??T
returns anOption
type and should be used if you want to return a value ornone
?none
and error), which are currently allowed in?
functions, are deprecated?See also #14664
Beta Was this translation helpful? Give feedback.
All reactions