Nothing is transferred: both ends are this process, and the value is
passed. The slice still runs where it was placed — this is the .at()
that never actually left home and pays for a trip anyway.
Never inferred. Whoever registers a host says it is in-process; a
broker that worked it out by comparing addresses would quietly undo the
reason a worker is a separate process, which is the GIL.
Whether two hosts given this same path are one place, and so share
one wire and one catalog.
It matters more than it looks. A worker has one catalog, and half of
one is a different catalog: provisioning the same process twice, once
per host name, swaps what it had live and takes every activation over
there with it. Getting this wrong is not an extra socket, it is a run
that quietly loses its state.
An address is an identity: the same host and port is the same
process. A command is not — it is a thing to run, and running it
twice gives two of them.