Ambiguous associated type when using associated_type_bounds feature #76593
Labels
C-bug
Category: This is a bug.
D-incorrect
Diagnostics: A diagnostic that is giving misleading or incorrect information.
F-associated_type_bounds
`#![feature(associated_type_bounds)]`
requires-nightly
This issue requires a nightly compiler in some way.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
produces an ambiguous, and nonsensical, associated type error even though
Blob
is introduced only once viaLoad
:If the use of associated type bounds is removed and replaced by equivalent
where
clauses, the problem goes away. This version compiles without error:FWIW in this codebase it looks like associated types could save quite a lot of boilerplate, as these will be quite common type bounds. So if you have a better idea how to do this, I'd love to hear!
Meta
rustc --version --verbose
:The text was updated successfully, but these errors were encountered: