Goroutines and channels versus ownership-based concurrency

WHAT THIS TESTS It checks whether you understand that Go and Rust attack concurrency safety from different layers: Go through runtime-provided primitives and convention, Rust through the type system.

A GOOD ANSWER COVERS Go's model is rooted in Communicating Sequential Processes. Goroutines are cheap, runtime-scheduled units of execution, and channels are typed conduits for passing values between them. The guiding maxim is to share memory by communicating rather than communicating by sharing memory, which encourages designs that avoid shared mutable state. However, Go does not stop you from sharing a pointer or map across goroutines, so data races remain possible and are caught only by the runtime race detector during testing. Rust takes a static approach: ownership ensures single ownership, borrowing forbids simultaneous aliasing and mutation, and the Send and Sync traits bound which types may cross or be shared across thread boundaries. Code that would race fails to compile, forcing explicit synchronization via Arc, Mutex, channels, or atomics.

WHAT EACH PREVENTS Go aims to reduce races by steering toward message passing but relies on discipline and tooling. Rust aims to eliminate data races outright at compile time. Neither prevents deadlocks, livelocks, or higher-level logic races.

COMMON WRONG ANSWERS Saying Go channels make data races impossible. Saying Rust prevents deadlocks. Treating Send and Sync as runtime constructs.

LIKELY FOLLOW-UPS How does the Go scheduler map goroutines to threads? How do you share state safely in each language? Does Rust have channels too? (Yes, in std and crates like crossbeam and tokio.)

ONE CONCRETE EXAMPLE Two goroutines writing to a shared map without a mutex compile fine in Go and may panic or corrupt data at runtime; go test -race surfaces it. The analogous Rust attempt to mutate shared data across threads without Arc<Mutex<...>> fails the borrow checker, so the bug never ships; once you wrap the data correctly, the access is provably race-free.