[erlang-questions] handle_info stopped crashing if no match?

[Vans S]

Is there anyway to disable this behavior (the handle_info if not defined producing a warning). I consider it a regression at this point because it has actually wasted a few hours of my time already debugging running large systems with many components as new features were being added. 

    On Sunday, February 25, 2018 12:06 PM, Michael Uvarov <freeakk@REDACTED> wrote:
 

 Unknown messages will come if you have a call, that timeouts and you catch an error.

On Sun, 25 Feb 2018, 16:38 Steve Strong, <steve@REDACTED> wrote:

Unless you’re comparing binaries for equality, in which case =:= is vastly more performant than ==, although I believe this has been fixed in a recent pull request...

Sent from my iPhone

> On 25 Feb 2018, at 15:23, Anthony Ramine <n.oxyde@REDACTED> wrote:
>
> There is absolutely no such performance benefit if at least one of the operands is known to not be an integer, the compiler optimises that.
>
>> Le 25 févr. 2018 à 11:38, Mikael Pettersson <mikpelinux@REDACTED> a écrit :
>>
>> Generally use the exact operations =:= and =/= unless you're certain
>> you want the variants with implicit numerical conversions.  There's
>> also a slight performance benefit to the exact operations.
>
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://erlang.org/mailman/listinfo/erlang-questions
_______________________________________________
erlang-questions mailing list
erlang-questions@REDACTED
http://erlang.org/mailman/listinfo/erlang-questions

_______________________________________________
erlang-questions mailing list
erlang-questions@REDACTED
http://erlang.org/mailman/listinfo/erlang-questions


   
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20180227/6e756944/attachment.htm>