Is it possible to implement methods on type aliases?

by

Is there any fix

Not really. A type alias (type Foo = Bar) does not create a new type. All it does is create a different name that refers to the existing type.

In Rust, you are not allowed to implement inherent methods for a type that comes from another crate.

another way for me to implement

The normal solution is to create a brand new type. In fact, it goes by the name newtype!

struct Link(Option<Box<Node>>);

impl Link {
    // methods all up in here
}

There’s no runtime disadvantage to this – both versions will take the exact same amount of space. Additionally, you won’t accidentally expose any methods you didn’t mean to. For example, do you really want clients of your code to be able to call Option::take?

Another solution is to create your own trait, and then implement it for your type. From the callers point of view, it looks basically the same:

type Link = Option<Box<Node>>;

trait LinkMethods {
    fn cool_method(&self);
}

impl LinkMethods for Link {
    fn cool_method(&self) {
        // ...
    }
}

The annoyance here is that the trait LinkMethods has to be in scope to call these methods. You also cannot implement a trait you don’t own for a type you don’t own.

See also:

More Related Contents:

  1. What is the difference between iter and into_iter?
  2. How can I swap in a new value for a field in a mutable reference to a structure?
  3. How does for syntax differ from a regular lifetime bound?
  4. Why is this match pattern unreachable when using non-literal patterns?
  5. How to convert a String into a &’static str
  6. Proper way to return a new string in Rust
  7. Double mutable borrow error in a loop happens even with NLL on
  8. How to return a reference to a sub-value of a value that is under a mutex?
  9. Is it possible to make a type only movable and not copyable?
  10. How can this instance seemingly outlive its own parameter lifetime?
  11. How to use struct self in member method closure
  12. How do I call a function through a member variable?
  13. How do you pass a Rust function as a parameter?
  14. Why does removing return give me an error: expected type `()` but found type
  15. Linking the lifetimes of self and a reference in method
  16. How do I fix “cannot find derive macro in this scope”?
  17. Thread ” has overflowed its stack when allocating a large array using Box
  18. Why is the bound `T: ‘a` required in order to store a reference `&’a T`?
  19. How do you enable a Rust “crate feature”?
  20. How to implement Iterator yielding mutable references [duplicate]
  21. How can a Rust program access metadata from its Cargo package?
  22. How can the ref keyword be avoided when pattern matching in a function taking &self or &mut self?
  23. Expected bound lifetime parameter, found concrete lifetime [E0271]
  24. How do I change a function’s qualifiers via conditional compilation?
  25. How do I print an integer in binary with leading zeros?
  26. What does Rust’s unary || (parallel pipe) mean?
  27. How does Rust’s type inference work across multiple statements?
  28. Why does Valgrind not detect a memory leak in a Rust program using nightly 1.29.0?
  29. What is the null pointer optimization in Rust?
  30. How to pass rustc flags to cargo?

Leave a Comment