Expose iterators over an inference result's types #20683
Conversation
This file contains hidden or 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
(This re-introduces a reduced access to a couple of previously public fields on `InferenceResult`)
rustbot
added
the
S-waiting-on-review
|
Maybe add a comment so that they won't be removed again? |
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 re-introduces a reduced access to a couple of previously public fields on
InferenceResult)As per: #20184 (comment)
@ChayimFriedman2: For my use case I don't really need to distinguish between the different origins of such types, but in order to provide an API that isn't only useful to my use case I've instead added individual iterators, rather than one composite chained one. Lemme know if you had something else in mind though and I'll happily make changes.