What "cloud memory costs"? Most Rust code is an informally-specified version of the old Python reference-counting GC. That's how you're supposed to write it, with clone() everywhere, and then dropping down to optimize. You can do the same thing with Go in the other direction by writing an allocator.

People believe a lot of weird things about these languages.

Why would I roll custom allocation strategies in Go (and then be accountable for supporting them) that affect multiple teams and services when I can have an LLM port to Rust and get dozens of additional benefits?

Depends on whether you'll ever need to use a mutable shared tree structure in your project, I guess.

But do remember that the logic you're using depends on nobody on your team reading the LLM code. If you're close-reading LLM outputs, all the complexity of Rust's memory management model is back on the table.