I think an interesting cultural difference between Rust and Go is that Rust is a 'sufficiently smart compiler' language and Go isn't. In other words, in Rust, it's idiomatic to create an enormous chain of function calls and assume that the compiler will boil it down to an efficient loop in release builds. In Go, you generally write code as if for a dumb compiler (even though the Go compiler is pretty sophisticated by now). If you want the code to compile down to an efficient loop, you just write the damn loop. There are advantages and disadvantages to both approaches.