Yeah, there's a mismatch in vocabulary between Go and Rust developers. In Go, `if err != nil { return nil, fmt.Errorf(...) }` is considered handling an error.

Yeah, there's a mismatch in vocabulary between Go and Rust developers. In Go, `if err != nil { return nil, fmt.Errorf(...) }` is considered handling an error. In Rust, the equivalent `.context(...)?` is considered passing an error. Handling it is about finding out what happened and doing something about it.