Skip to content

Comment on Understanding Real-World Concurrency Bugs in Go [pdf]parent

Comments

Erlang runs atop its own VM that includes scheduler, routing services, etc.

There are (at least) a couple of different ways to identify the recipient of a message: process ID (unique identifier for another actor) or Erlang's name service.

The VM does indeed know whether the recipient is local; the sender typically neither knows nor cares, although the information is available if useful.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.