5 ms·

i like the pattern, but message passing where the message is actually just a pointer to a mutable struct ( as allowed in go) kind of defeat the purpose, doesn't

• superb_dev 2y ago
  It kinda does yeah, you probably shouldn’t do that
  • adastra22 2y ago
    It’s fine if that’s the only (writable) pointer to the struct. Which is something go doesn’t enforce, but Rust does. I often dream of Go with Rust’s borrow checker. Sigh…
    • jimbokun 2y ago
      Wouldn't that be Rust?
      • adastra22 2y ago
        Rust doesn’t have a direct analogue to go’s concurrency primitives. The pieces are there, but you have to jump through hoops to use them effectively.
• dgb23 2y ago
  No, it’s an idiomatic way of expressing who’s in charge of a given piece of data. There’s nothing in the type system preventing data races. But that’s orthogonal to channels. They just help you to structure the code.