Is there any way to restrict a generic type to one of several types?

by

For references into an array usually you’d just use a usize rather than different integer types.

However, to do what you are after you can create a new trait, implement that trait for u16, u32 and u64 and then restrict T to your new trait.

pub trait MyNewTrait {}

impl MyNewTrait for u16 {}
impl MyNewTrait for u32 {}
impl MyNewTrait for u64 {}

struct Foo<T: MyNewTrait> { ... }

You may then also add methods onto MyNewTrait and the impls to encapsulate the logic specific to u16, u32 and u64.

More Related Contents:

  1. Traits and Rust
  2. Why do try!() and ? not compile when used in a function that doesn’t return Option or Result?
  3. Why does linking lifetimes matter only with mutable references?
  4. How do I collect into an array?
  5. Cannot borrow as mutable more than once at a time in one code – but can in another very similar
  6. Is it considered a bad practice to implement Deref for newtypes?
  7. Implementing a trait for multiple types at once
  8. How do I get an owned value out of a `Box`?
  9. How can I store a Chars iterator in the same struct as the String it is iterating on?
  10. Converting from Option to Option
  11. How to disable unused code warnings in Rust?
  12. Why doesn’t println! work in Rust unit tests?
  13. How do you use parent module imports in Rust?
  14. Why is the `Sized` bound necessary in this trait?
  15. How do I overcome match arms with incompatible types for structs implementing same trait?
  16. Example of how to use Conditional Compilation Macros in Rust
  17. How to take ownership of T from Arc?
  18. Is there any trait that specifies numeric functionality?
  19. Why do I get “type annotations needed” when using Iterator::collect?
  20. Why would I use divergent functions?
  21. How to generate statically linked executables?
  22. When is it necessary to circumvent Rust’s borrow checker?
  23. How to idiomatically alias a crate in Rust 2018?
  24. Cannot borrow immutable borrowed content as mutable
  25. Why do I get “does not live long enough” in a return value?
  26. Why does the compiler not complain that an iterator moved to a for loop is immutable?
  27. Removing items from a BTreeMap or BTreeSet found through iteration
  28. Why doesn’t the lifetime of a mutable borrow end when the function call is complete?
  29. Lazy sequence generation in Rust
  30. Is there a way to get the field names of a struct in a macro?

Leave a Comment