[erlang-questions] why does rpc:call do this?

[Cian Synnott]

On Wed, Jul 13, 2016 at 2:09 AM, Cian Synnott <cian@REDACTED> wrote:
> I *think* that's just to properly handle reporting back to the client
> when the apply/3 subprocess blows up for some reason.
>
FWIW, it looks like the current RPC server behaves more like you
expected, cutting out some messages:

  https://github.com/erlang/otp/blob/maint/lib/kernel/src/rpc.erl#L178

and continues to do the cleanup & error reporting parts in handle_info:

  https://github.com/erlang/otp/blob/maint/lib/kernel/src/rpc.erl#L133

It uses maps rather than a gb_trees, too. :o)

Cian