implied_bounds_entailment
diagnostic when associated type not in scope
#112321
Labels
A-diagnostics
Area: Messages for errors, warnings, and lints
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Uh oh!
There was an error while loading. Please reload this page.
Code
Current output
Desired output
Rationale and extra context
When implementing the trait, if the associated type is set to something that is not in scope / doesn't exist, the compiler emits a
implied_bounds_entailment
diagnostic. I don't think this should be emitted because there is no way to calculate a type's trait bounds when it doesn't even exist.Might be related to #108544, but I decided to file a separate issue because this does not involve any lifetimes.
Other cases
No response
Anything else?
Tested with stable 1.70.0, beta 1.71.0-beta.1 and nightly 1.72.0-nightly (d59363a 2023-06-01)
The text was updated successfully, but these errors were encountered: