Can’t implement a trait I don’t own for all types that implement a trait I do own

by

I should be able to implement Rand for AllValues since AllValues is defined in my crate.

No, you are only allowed to implement your own trait AllValues for types you didn’t define. You can’t make the logical jump to implementing an unrelated trait that you also didn’t define.

There are two considerations to remember:

  • If your trait is public (which it is based on the code you’ve provided), you aren’t the only one that can implement the trait. Consumers of your crate might be able to implement it for their own types, where they might also decide to implement Rand!
  • The rand crate might decide to implement Rand for T some time in the future.

What is the right way to implement Rand for things that implement AllValues?

I don’t believe there is one. I’d just introduce a wrapper type that holds a value or a reference to a value that implements your trait and implement Rand for that.

See also:

More Related Contents:

  1. Traits and Rust
  2. How to get a reference to a concrete type from a trait object?
  3. Why can impl trait not be used to return multiple / conditional types?
  4. How do I implement a trait I don’t own for a type I don’t own?
  5. What makes something a “trait object”?
  6. Is it possible to use `impl Trait` as a function’s return type in a trait definition?
  7. How do I return an instance of a trait from a method?
  8. I implemented a trait for another trait but cannot call methods from both traits
  9. Why would I implement methods on a trait instead of as part of the trait?
  10. How does the mechanism behind the creation of boxed traits work?
  11. Trait implementation for both a trait object and for direct implementors of the trait
  12. Why is the `Sized` bound necessary in this trait?
  13. How can I implement Rust’s Copy trait?
  14. Is there any trait that specifies numeric functionality?
  15. Understanding Traits and Object Safety
  16. How do I pass a closure through raw pointers as an argument to a C function?
  17. How do I specify that a struct field must implement a trait?
  18. Rust equivalent to Swift’s extension methods to a protocol?
  19. Cannot use moved BufReader after for loop with bufreader.lines()
  20. Do I have to implement a trait twice when implementing it for both reference and non-reference types?
  21. Return local String as a slice (&str)
  22. How to convert a String into a &’static str
  23. Weird behaviour when using read_line in a loop
  24. How can this instance seemingly outlive its own parameter lifetime?
  25. What do I have to do to solve a “use of moved value” error?
  26. Why does removing return give me an error: expected type `()` but found type
  27. Linking the lifetimes of self and a reference in method
  28. What is an auto trait in Rust?
  29. Why is Rust’s assert_eq! implemented using a match?
  30. How can I conditionally provide a default reference without performing unnecessary computation when it isn’t used?

Leave a Comment