Hacker News Reader

But go doesn't provide channels in the CSP way nor does it do any model checking on it right?

Like one thing it already gets wrong is that you can send mutable pointers around without clear ownership.

If it's 'wrong' to be able to pass around mutable pointers, is the only language that is 'right' Rust? (and some Lisps maybe?)

I think you can do "real" ownership in ATS; or check ownership with a static analysis tool in many languages, including C; and you should be able make a hacky version as a library that dies at runtime in any language with parametric polymorphism and modules. "Modern C++" too, ish.

Which Lisps are you thinking of? CL and Scheme both allow having multiple copies of mutable objects.

No. For example Erlang only allows you to send immutable values around. For very good reason.

Reply on news.ycombinator.com