Confusing error message when using `min_specialization` with `dyn Trait`
Open
Nobody has claimed this yet.
A-diagnostics
A-specialization
F-min_specialization
requires-nightly
T-compiler
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
I tried this code:
#![feature(min_specialization)]
pub trait Foo {
fn foo(&self);
}
impl<T> Foo for T {
default fn foo(&self) {}
}
impl Foo for Box<dyn Foo> {
fn foo(&self) {}
}
This failed to compile with
error: cannot specialize on `'static` lifetime
--> src/lib.rs:15:1
|
15 | impl Foo for Box<dyn Foo> {
| ^^^^^^^^^^^^^^^^^^^^^^^^^
This seems weird since there isn't a visible lifetime anywhere. The error should explain that the 'static lifetime is implicit on dyn Foo and suggest adding a lifetime parameter.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the example in src/lib.rs and examining the compiler diagnostic for the impl using Box. Trace the specialization and implicit-lifetime handling involved in that diagnostic. Done means the error explains that dyn Foo implies a 'static lifetime and suggests adding a lifetime parameter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100