Currently, Elixir behaviours accept 3 ways of naming a process - a simple atom,
a {:global, name} tuple, and a {:via, registry, name} one. While it's fine, the
global naming always bothered me - being this special snowflake wrapped in it's
own tuple.
Exactly the same behaviour of passing {:global, name} is achieved by passing
{:via, :global, name}. I propose we deprecate the global tuple in favour of
the via tuple.
This allows reducing the amount of ideas there are to learn when first meeting
processes by one thing, and we all know there are already many. Additionally
this would leave a consistent scheme for calling gen* processes: an atom name,
a two-tuple for locally registered process on another node, and a via tuple for
registries.
Michał.
--
You received this message because you are subscribed to the Google Groups
"elixir-lang-core" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elixir-lang-core/c782e8f3-1ae4-4e6b-a36f-2081ddf17e00%40Spark.
For more options, visit https://groups.google.com/d/optout.
