This Week in Rust – Static linking, Win64

Re:This Week in Rust – Static linking, Win64 by pcwalton on Monday December 02, 2013 @02:46AM (#6832371)

> Rust provides separate heaps per "task" and a data ownership system which means you never end up sharing state between "tasks" (ala Erlang).

Nitpick: This isn't actually true. Rather Rust ensures at compile time that if you share memory you can't race on it (either you share only immutable data, or you take a lock whenever you mutate). This is one of the things that makes Rust unique among industry languages: you get shared memory and data race freedom.

[ Parent | on HN ]

Re:This Week in Rust – Static linking, Win64 by derefr on Monday December 02, 2013 @03:27AM (#6832490)

Technically, you also get shared memory in Erlang--it's just table-structured rather than a block of raw bytes. I've never really come across a situation in Erlang, that calls for shared memory in other languages, that sharing an ETS table and passing messages about events on it doesn't solve more cleanly.

[ Parent | on HN ]

Re:This Week in Rust – Static linking, Win64 by sanxiyn on Monday December 02, 2013 @07:54AM (#6833295)

I think that makes sense. Shared memory is mainly a performance optimization. Erlang is not known to have C++-like speed, so if it is fast enough to do in Erlang, it probably is fast enough so that shared memory is not needed.

[ Parent | on HN ]