Could you explain a bit more about how you see Golang improving this? For me, Go is trickier to use concurrently than Rust, and requires keeping track of more

Could you explain a bit more about how you see Golang improving this? For me, Go is trickier to use concurrently than Rust, and requires keeping track of more details you need to manage yourself without compiler assistance or checking. For example, the default data structures like Map are not thread-safe, but you'll only discover that you've used a Map from multiple threads without synchronization when you actually have a concurrent modification at runtime, which might not show up at low load during testing. You're also responsible for explicitly locking (and unlocking) any synchronization primitives before accessing a synchronized resource, and ensuring you don't hold any references to synchronized data past the unlock. With Rust, this is all encoded in the APIs, and verified by either the type checker or the borrow checker. Since I need to deal with Golang at work, I've been trying to get less frustrated with it, so I'm really interested in hearing perspectives about what people appreciate about Golang, or what it does right or does well.