handle the "no limiter" case more obviously

This is no semantic change since gen_server:cast(undefined, ...)
returns 'ok'. However, it only does so because it catches the 'badarg'
error thrown by erlang:send. It is probably more efficient to not
attempt the send in the first place. Plus for documentation purposes,
and to keep dialyzer happy, it is useful to state explicitly which
functions are expected to be called on an 'undefined' limiter.

0 files changed, 0 insertions, 0 deletions