upvote
Maybe, but whatever workarounds or compromises the LLM has to settle on to satisfy the borrow checker will live in the code forever, while garbage collection can continue to get faster in the same executable.
reply
Rust code tend to be "better" because those concerns forces the architecture upfront and guaranteed that nothing breaks later on.
reply
Eh. In my experience any long-running Rust project will go through a lot of refactors, often driven by borrow checker issues. The only bright spot is that the compiler makes them relatively easy and safe. But it would be better not to have to do them in the first place if your architecture is already solid, just not in a way that the borrow checker understands.
reply
The same arguments could often apply to Zig with 100% up-front static allocation (like TigerBeetle uses).
reply