When Should I Use 'static vs a Named Lifetime?

Use static when a reference must live for the entire duration of the program, such as for string literals or global data; use a named lifetime (e.g., 'a) when you need to relate the lifetimes of multiple references to ensure they don't outlive the data they point to. Named lifetimes are required for functions or structs that borrow data from arguments or fields, whereas static is a specific, fixed lifetime bound to the binary.

// Use 'static for string literals (data lives forever)
fn greet() -> &'static str {
    "Hello, world!"
}

// Use named lifetime 'a to tie the output reference to the input reference
fn longest<'a>(x: &'a str, y: &'a str) -> &'a str {
    if x.len() > y.len() { x } else { y }
}

Think of static as a promise that data exists from the very start to the very end of your program, like a permanent sign on a building. A named lifetime is a flexible rule you create to ensure two or more references stay valid for the same amount of time, preventing you from pointing to data that has already been deleted. Use static for constants and use named lifetimes when passing references around in functions.