“Expected type parameter” error in the constructor of a generic struct

by

Here’s a reproduction of your error:

struct Foo<T> {
    val: T,
}

impl<T> Foo<T> {
    fn new() -> Self {
        Foo { val: true }
    }
}

fn main() {}

The problem arises because you tried to lie to the compiler. This code:

impl<T> Foo<T> {
    fn new() -> Self {
        /* ... */
    }
}

Says “For whatever T the caller chooses, I will create a Foo with that type”. Then your actual implementation picks a concrete type — in the example, a bool. There’s no guarantee that T is a bool. Note that your new function doesn’t even accept any parameter of type T, which is highly suspect as that’s how the caller picks the concrete type 99% of the time.

The correct way of saying this would be

impl Foo<bool> {
    fn new() -> Self {
        Foo { val: true }
    }
}

Although you probably want to pick a more specific name than new, as it looks as if you are trying to make your struct generic. Presumably there would be other constructors with different types.

For your exact code, you probably want something like

impl TextureFactory<gfx_device_gl::Resources> { /* ... */ }

Another possible solution would be to remove the generic type parameter from your struct. If you only ever construct it with a gfx_device_gl::Resources, then there’s no reason to make it generic.

In other cases, you may be trying to return a type that implements a trait. For that, you can use a boxed trait object:

impl Foo<Box<dyn std::fmt::Display>> {
    fn new() -> Self {
        Foo { val: Box::new(true) }
    }
}

In the future, you may also be able to use impl Trait (a.k.a. existential types):

#![feature(type_alias_impl_trait)]

struct Foo<T> {
    val: T,
}

type SomeConcreteButOpaqueType = impl std::fmt::Display;

impl Foo<SomeConcreteButOpaqueType> {
    fn new() -> Self {
        Foo { val: true }
    }
}

See also:

More Related Contents:

  1. How do I use integer number literals when using generic types?
  2. How can I avoid a ripple effect from changing a concrete struct to generic?
  3. The trait cannot be made into an object
  4. Conflicting implementations of trait in Rust
  5. Generics Error: expected type parameter, found struct
  6. Why can’t I add a blanket impl on a trait with a type parameter?
  7. Can I avoid eager ambiguity resolution for trait implementations with generics?
  8. What is the cited problem with using generic type parameters in trait objects?
  9. How do I require a generic type implement an operation like Add, Sub, Mul, or Div in a generic function?
  10. How to write a trait bound for adding two references of a generic type?
  11. How do I write the lifetimes for references in a type constraint when one of them is a local reference?
  12. Why does a generic method inside a trait require trait object to be sized?
  13. How do I return a Filter iterator from a function?
  14. Matching a generic parameter to an associated type in an impl
  15. Why can’t I use a key function that returns a reference when sorting a vector with sort_by_key?
  16. Why can’t `&(?Sized + Trait)` be cast to `&dyn Trait`?
  17. What does the question mark mean in a type parameter bound?
  18. What does it mean to instantiate a Rust generic with an underscore?
  19. Writing a generic function that takes an iterable container as parameter in Rust
  20. How do I unwrap an arbitrary number of nested Option types?
  21. Unable to create a polymorphic type because the trait cannot be made into an object
  22. How to get a reference to a concrete type from a trait object?
  23. How does the reified keyword in Kotlin work?
  24. How do I return an instance of a trait from a method?
  25. Why would I implement methods on a trait instead of as part of the trait?
  26. Scala 2.8 CanBuildFrom
  27. Generic higher order function
  28. How to determine if a generic is an optional in Swift?
  29. How do I specify that a struct field must implement a trait?
  30. Returning original collection type in generic method

Leave a Comment