Copy types in Rust

Introduction

Copy types let you make quick copies of simple data without extra work. This helps keep your code easy and fast.

When you want to duplicate small values like numbers or characters.

When you need to pass data to functions without moving ownership.

When you want to avoid manual cloning for simple data.

When working with fixed-size data that is cheap to copy.

Syntax

Rust

#[derive(Copy, Clone)]
struct MyType {
    value: i32,
}

fn main() {
    let a = MyType { value: 5 };
    let b = a; // b is a copy of a
}

Types must implement both Copy and Clone traits to be copy types.

Copy types are copied automatically on assignment or passing to functions.

Examples

Simple integer values are copy types by default.

Rust

let x = 10;
let y = x; // x is copied to y

Custom structs can be copy types if they derive Copy and Clone.

Rust

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

fn main() {
    let p1 = Point { x: 1, y: 2 };
    let p2 = p1; // p1 is copied to p2
}

Types like String are not copy types because copying them is expensive.

Rust

let s1 = String::from("hello");
// let s2 = s1; // This moves s1, not copies
// To copy, you must clone: let s2 = s1.clone();

Sample Program

This program shows how a struct with Copy can be assigned to another variable without moving ownership.

Rust

#[derive(Copy, Clone, Debug)]
struct Color {
    red: u8,
    green: u8,
    blue: u8,
}

fn main() {
    let c1 = Color { red: 255, green: 0, blue: 0 };
    let c2 = c1; // c1 is copied to c2
    println!("c1: {:?}", c1);
    println!("c2: {:?}", c2);
}

Important Notes

Copy types are best for small, simple data that is cheap to copy.

Using Copy avoids ownership moves, making code easier to read.

Not all types can be Copy; complex types like vectors or strings need cloning.

Summary

Copy types automatically duplicate data on assignment or passing.

They require implementing both Copy and Clone traits.

Use copy types for simple, small data to keep code simple and efficient.

Practice

1. Which of the following types in Rust is a Copy type by default?

easy

A. A String

B. An integer like i32

C. A vector like Vec<i32>

D. A struct with a String field

Solution

1. Step 1: Identify primitive types with Copy trait

   Primitive scalar types like integers (i32) implement Copy by default.

2. Step 2: Understand ownership of heap data

   Types like String and Vec own heap data and do not implement Copy automatically.

3. Final Answer:

   An integer like i32 -> Option B

4. Quick Check:

   Primitive types = Copy [OK]

Hint: Primitive scalars like i32 are Copy by default [OK]

Common Mistakes:

• Thinking String is Copy because it looks simple
• Assuming all structs are Copy without checking fields
• Confusing heap-allocated types with Copy types

2. Which syntax correctly derives the Copy trait for a struct in Rust?

easy

A. struct Point { x: i32, y: i32 } // Copy is automatic

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

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

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

Solution

1. Step 1: Recall trait derivation rules

   To make a struct Copy, you must derive both Copy and Clone traits.

2. Step 2: Check each option

   #[derive(Copy, Clone)] struct Point { x: i32, y: i32 } correctly derives both traits. #[derive(Clone)] struct Point { x: i32, y: i32 } misses Copy. struct Point { x: i32, y: i32 } // Copy is automatic is wrong because Copy is not automatic for structs. #[derive(Copy)] struct Point { x: i32, y: i32 } misses Clone.

3. Final Answer:

   #[derive(Copy, Clone)] struct Point { x: i32, y: i32 } -> Option C

4. Quick Check:

   Copy requires Copy + Clone traits [OK]

Hint: Always derive both Copy and Clone for Copy types [OK]

Common Mistakes:

• Deriving only Copy without Clone
• Assuming Copy is automatic for structs
• Forgetting to derive Clone along with Copy

3. What will be the output of this Rust code?

#[derive(Copy, Clone)]
struct Color(u8, u8, u8);

fn main() {
    let c1 = Color(255, 0, 0);
    let c2 = c1;
    println!("{} {} {}", c1.0, c1.1, c1.2);
}

medium

A. 255 0 0

B. Compile error: use of moved value

C. 0 0 0

D. Runtime panic

Solution

1. Step 1: Understand Copy trait effect on assignment

   Since Color derives Copy, assigning c1 to c2 copies the data, not moves it.

2. Step 2: Check usage after assignment

   Because c1 is still valid, printing its fields outputs the original values.

3. Final Answer:

   255 0 0 -> Option A

4. Quick Check:

   Copy means no move, data duplicated [OK]

Hint: Copy types allow use after assignment without move errors [OK]

Common Mistakes:

• Expecting a move error after assignment
• Thinking c1 is invalid after c2 = c1
• Confusing Copy with Clone behavior

4. Identify the error in this Rust code snippet:

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

fn main() {
    let p1 = Point { x: 5, y: 10 };
    let p2 = p1;
    println!("{} {}", p1.x, p1.y);
}

medium

A. Assignment moves ownership, so p1 is invalid

B. Cannot print struct fields directly

C. No error, code runs fine

D. Missing Clone trait derivation causes compile error

Solution

1. Step 1: Check trait derivations

   The struct derives only Copy, but Copy requires Clone to be implemented too.

2. Step 2: Understand compiler requirements

   Rust compiler will error because Clone is missing, even if Copy is derived.

3. Final Answer:

   Missing Clone trait derivation causes compile error -> Option D

4. Quick Check:

   Copy needs Clone too [OK]

Hint: Derive Clone along with Copy to avoid errors [OK]

Common Mistakes:

• Assuming Copy alone is enough
• Thinking printing fields causes error
• Confusing move error with trait error

5. You want to create a struct Pixel with fields x: u32, y: u32, and color: (u8, u8, u8). You want Pixel to be a Copy type. Which of the following is the correct approach?

hard

A. Derive Copy and Clone for Pixel since all fields are Copy types

B. Implement Copy manually without Clone

C. Use String for color and derive Copy

D. Derive only Clone for Pixel

Solution

1. Step 1: Check field types for Copy trait

   Fields u32 and tuple of u8 are all Copy types.

2. Step 2: Derive Copy and Clone for struct

   Since all fields are Copy, deriving both Copy and Clone for Pixel makes it a Copy type.

3. Final Answer:

   Derive Copy and Clone for Pixel since all fields are Copy types -> Option A

4. Quick Check:

   All fields Copy + derive Copy & Clone = Copy type [OK]

Hint: All fields Copy? Derive Copy and Clone for struct [OK]

Common Mistakes:

• Using String for color which is not Copy
• Deriving only Clone without Copy
• Trying to implement Copy manually