This helped congeal a thing I've been thinking about in my Rust usage for a long time, but didn't know how to express: > In Rust, this distinction in register

This helped congeal a thing I've been thinking about in my Rust usage for a long time, but didn't know how to express: > In Rust, this distinction in register can look like this: > - Will I use references and borrowing, or will I liberally use clone to avoid it? > In general, Rust strives to have an obvious register which to operate which is still going to be performant enough (and hopefully accessible enough!), while allowing users to switch register when they need to. One of the biggest ergonomics problems in Rust, in my experience, is that for certain things (like references vs clones, or generics vs enums vs dynamic dispatch), it can be very hard to change registers once you realize you need a different one. Often it means making changes throughout your entire codebase I don't have an easy solution but I feel like I at least have words for the problem now