Comment on Rust vs Go: A Hands-On ComparisonparentComments−Thaxll2yBut you're not comparing the same thing, Go handle errors and act on it, Rust code just "forward" the error.Control flow wise, Go is much easier to understand than chains of ? and await.−jamincan2yRust doesn't just forward the error, it forwards and converts the error. ? is effectively semantic sugar for:`match result { Ok(v) => v, Err(e) => return e.into() }`This means that the code related to error handling is all in one place, and your business logic can just focus on the happy path.
Comments
But you're not comparing the same thing, Go handle errors and act on it, Rust code just "forward" the error.
Control flow wise, Go is much easier to understand than chains of ? and await.
Rust doesn't just forward the error, it forwards and converts the error. ? is effectively semantic sugar for:
`match result { Ok(v) => v, Err(e) => return e.into() }`
This means that the code related to error handling is all in one place, and your business logic can just focus on the happy path.