Hi, coming from Node I try to learn idiomatic Rust code. Opposite to JavaScript Rust offers explicit or implicit returns, so I wonder what would be more idiomatic here? use std::error::Error; use std::fs::File; use std::io::Read; fn read_file(path: &str) -> String { let mut file = match File::…

I don't think that there are extremely strong feelings about this in the community, but I think that the variant without return is preferable. I myself avoid returns if possible. On the unrelated note, I think this error handling can be implemented more compactly as let mut file = File::open(path).…

[image] matklad: On the unrelated note, I think this error handling can be implemented more compactly as let mut file = File::open(path).unwrap_or_else(|_err| panic!("Coundn't open: {}", path)). Note that the err.description() string will not include the file name, which is most relevant here. …

Should the compiler warn for return in non-early returns just like it warns for not using snake_case?

There may be some exceptions, but in general the style things the compiler warns about seriously impact other users' ability to reason about code, because the case of an ident helps readers parse what sort of term it is (that is: variable, constant, type, etc). Style choices like whether or not to u…

Implicit or explicit return in non-closures. What is more idiomatic?

help

steveklabnik June 28, 2016, 8:09pm 4

The official style is "return is only for early returns."

Topic		Replies	Views
Enable linting for implicit returns help	24	3408	July 31, 2023
Clippy warnings to remove `return` a bit too much? code review	10	3319	January 17, 2021
Explicit and implicit return in functions	7	20587	April 1, 2022
Implicit vs Explicit community	20	3724	June 8, 2021
Explicit function exit markers	2	1097	December 2, 2015

Implicit or explicit return in non-closures. What is more idiomatic?

Related topics