Rust errors / Everything else
Rust compiler error · checked with rustc 1.99.0
Rust error E0193: #### Note: this error code is no longer emitted by the compiler
What it means#### Note: this error code is no longer emitted by the compiler.
Retired: rustc no longer emits this error code. You may still see it in old answers, books and CI logs from older toolchains; the explanation below is kept for reference.
The compiler team's explanation
Note: this error code is no longer emitted by the compiler.
where clauses must use generic type parameters: it does not make sense to use them otherwise. An example causing this error:
trait Foo {
fn bar(&self);
}
#[derive(Copy,Clone)]
struct Wrapper<T> {
Wrapped: T
}
impl Foo for Wrapper<u32> where Wrapper<u32>: Clone {
fn bar(&self) { }
}
This use of a where clause is strange - a more common usage would look something like the following:
trait Foo {
fn bar(&self);
}
#[derive(Copy,Clone)]
struct Wrapper<T> {
Wrapped: T
}
impl <T> Foo for Wrapper<T> where Wrapper<T>: Clone {
fn bar(&self) { }
}
Here, we're saying that the implementation exists on Wrapper only when the wrapped type T implements Clone. The where clause is important because some types will not implement Clone, and thus will not get this method.
In our erroneous example, however, we're referencing a single concrete type. Since we know for certain that Wrapper<u32> implements Clone, there's no reason to also specify it in a where clause.
From rustc --explain E0193 (1.99.0), part of the Rust project, MIT or Apache-2.0. Official page.
Related errors
- E0061this function takes N arguments but M were supplied
- E0412cannot find type in this scope
- E0515cannot return reference to local variable
- E0728await is only allowed inside async functions and blocks
- E0133call to unsafe function `f` is unsafe and requires unsafe function or block
- E0152found duplicate lang item `owned_box`
- E0264unknown external lang item: `copy`
- E0267`break` inside of a closure
Up next
Often hit nextE0061: this function takes N arguments but M were suppliedA related error from the same family.Read it next →Did this answer your question?