editoast: make 'Result' more flexible #7074
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When defining a new
Result
, it's sometimes annoying having aResult
available and trying to use it asResult<T, E>
but actually, there is only one generic argument.Replacing
type Result<T> = StdResult<T, InternalError>
bytype Result<T, E = InternalError> = StdResult<T, E>
keep the bonus of using a customResult
(always returning ourInternalError
) but leaving the possibility to opt-out easily by specifying the second generic argument.Note: this seems to alleviate the CI problem on #6791. If someone is willing to dig more why these two seemingly unrelated things seem to interact, please do and share, I'm curious.