neon: Remove JsResultExt #904
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
JsResultExt is redundant with ResultExt. They are identical traits except for an additional `V: Value` bound in `JsResultExt`.
dherman
approved these changes
Jun 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
JsResultExtis redundant withResultExt. They are identical traits except for an additionalV: Valuebound inJsResultExt.Having two traits presents the opportunity for ambiguous method resolution. This PR proposes that we take the opportunity before 1.0 to make a breaking change and remove
JsResultExt.As demonstrated in the diff, replacing a
JsResultExtimplementation withResultExtis as trivial as replacingJsResultExt<..>withResultExt<Handle<..>>.