RFC: Generic member access for dyn Error trait objects #3461
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
Co-authored-by: kennytm <[email protected]>
Co-authored-by: Adam Perry <[email protected]>
Co-authored-by: Adam Perry <[email protected]>
Co-authored-by: bstrie <[email protected]>
Closed
ehuss
added
the
T-libs-api
This was referenced Aug 24, 2023
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.
This PR is a duplicate of #2895, which I have agreed to take over for @yaahc. The idea is to close that in favor of this PR so I can drive additional changes as feedback comes in.
The current state of this proposal is as follows:
error_generic_member_accessfeature flag is available in nightly.provide_anytracking issue in nightly.provide_anyfeature by taking on theDemand/RequestAPI (minus theProvidertrait) for the sake of generic member access ondyn Error.Rendered