Eliminate the notion of "bound resolution" from inference.md. #4013
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.
In its place, the spec's definition of "T_0 bounded" is tightened up so that for any type T, there is exactly one type T_0 such that T is T_0 bounded. Then, instead of saying "let U_0 be the bound resolution of T_0", we can say "let U_0 be the unique type such that T_0 is U_0 bounded."
This avoids some redundancy, since we no longer need to define separate but related notions of "T_0 bounded" and "bound resolution".
Contribution guidelines:
dart format
.Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.