What is derive in Rust?

In the Rust programming language, derive is an attribute that allows the compiler to provide basic implementations for certain traits. These traits can still be manually implemented to achieve more complex behavior.

What Problem Does derive Solve?

The derive attribute solves the problem of writing large amounts of repetitive code when manually implementing certain traits. It enables the compiler to automatically generate basic implementations of these traits, reducing the amount of code developers need to write.

How to Use derive?

To use the derive attribute, simply add #[derive(...)] to the type definition (such as a struct or enum). The ... inside the brackets represents the list of traits for which a basic implementation should be provided.

For example, the following code snippet demonstrates how to use derive to implement the PartialEq and Debug traits:

#[derive(PartialEq, Debug)]
struct Point {
    x: f64,
    y: f64,
}

fn main() {
    let p1 = Point { x: 1.0, y: 2.0 };
    let p2 = Point { x: 1.0, y: 2.0 };
    assert_eq!(p1, p2);
    println!("{:?}", p1);
}

Commonly Used derive Attributes

There are many commonly used traits that can be implemented via derive, including comparison traits (Eq, PartialEq, Ord, PartialOrd), cloning traits (Clone), and debugging traits (Debug). These traits can also be manually implemented to achieve more complex behavior.

Below are code examples demonstrating how these derive attributes work.

Eq and PartialEq

These two traits are used to compare whether two values are equal. PartialEq allows partial equality, while Eq requires complete equality.

Here is a simple example demonstrating how to use derive to implement these two traits:

#[derive(PartialEq, Eq)]
struct Point {
    x: i32,
    y: i32,
}

fn main() {
    let p1 = Point { x: 1, y: 2 };
    let p2 = Point { x: 1, y: 2 };
    assert_eq!(p1, p2);
}

Ord and PartialOrd

These two traits are used to compare the ordering of two values. PartialOrd allows partial ordering, while Ord requires complete ordering.

Here is a simple example demonstrating how to use derive to implement these two traits:

#[derive(PartialOrd, Ord)]
struct Point {
    x: i32,
    y: i32,
}

fn main() {
    let p1 = Point { x: 1, y: 2 };
    let p2 = Point { x: 2, y: 1 };
    assert!(p1 < p2);
}

Copy

This trait is used to create a copy of a value. It allows creating a new instance of T from &T.

When you assign one variable to another, if the type implements the Copy trait, a new copy of the value is created. This is different from move semantics, where the original variable is no longer available.

To use the derive attribute to automatically generate an implementation of the Copy trait, simply add #[derive(Copy)] before the type definition. For example:

#[derive(Copy)]
struct Point {
    x: i32,
    y: i32,
}

fn main() {
    let p1 = Point { x: 1, y: 2 };
    let p2 = p1;
    assert_eq!(p1.x, p2.x);
    assert_eq!(p1.y, p2.y);
}

Note that not all types can implement the Copy trait. For example, types that contain heap-allocated fields (such as String or Vec<T>) cannot implement Copy. Additionally, if a type implements the Drop trait, it also cannot implement Copy. This is because when a value is dropped, its destructor is called, and if the value also implements Copy, the destructor might be called multiple times, potentially leading to undefined behavior.

If you want to enable copying for types that allocate resources on the heap, you should use Clone instead.

Clone

This trait is used to create a copy of a value. It allows creating a new instance of T from &T.

Almost all types can implement the Clone trait. The Clone trait provides a clone method, which is used to create a deep copy of an instance.

Unlike the Copy trait, Clone does not require bitwise copy semantics. This means that even if a type has heap-allocated fields (such as String or Vec<T>), it can still implement Clone.

To automatically generate an implementation of the Clone trait for a type, simply add #[derive(Clone)] before the type definition. For example:

#[derive(Clone)]
struct Point {
    x: i32,
    y: i32,
}

fn main() {
    let p1 = Point { x: 1, y: 2 };
    let p2 = p1.clone();
    assert_eq!(p1.x, p2.x);
    assert_eq!(p1.y, p2.y);
}

However, not all types can automatically derive the Clone trait. If some fields of a type do not implement Clone, you need to manually implement Clone for that type.

Debug

This trait is used to generate a debug string representation of a value.

Here is a simple example demonstrating how to use derive to implement this trait:

#[derive(Debug)]
struct Point {
    x: i32,
    y: i32,
}

fn main() {
    let p = Point { x: 1, y: 2 };
    println!("{:?}", p);
}

What Are the Drawbacks and Limitations of derive?

Although using the derive attribute allows for quickly generating basic implementations of certain traits, it has some drawbacks and limitations. Firstly, since the compiler automatically generates implementations, they may not be complex enough. If you need more advanced behavior, you will have to manually implement these traits. Additionally, derive can only be used for certain predefined traits and cannot be applied in all situations.

Hopefully, this article helps you better understand the derive feature in Rust.

---

We are Leapcell, your top choice for hosting Rust projects.

Leapcell is the Next-Gen Serverless Platform for Web Hosting, Async Tasks, and Redis:

Multi-Language Support

• Develop with Node.js, Python, Go, or Rust.

Deploy unlimited projects for free

• pay only for usage — no requests, no charges.

Unbeatable Cost Efficiency

• Pay-as-you-go with no idle charges.
• Example: $25 supports 6.94M requests at a 60ms average response time.

Streamlined Developer Experience

• Intuitive UI for effortless setup.
• Fully automated CI/CD pipelines and GitOps integration.
• Real-time metrics and logging for actionable insights.

Effortless Scalability and High Performance

• Auto-scaling to handle high concurrency with ease.
• Zero operational overhead — just focus on building.

Explore more in the Documentation!

Follow us on X: @LeapcellHQ