> > 2. The default implementation of handle_info/1 will exit on any incoming > message, in the same way handle_cast/2 and handle_call/3 already do. >
I believe this is not a good default because your processes may receive regular messages from other processes and you don't want to crash because of them. This is much more unlikely to happen with cast and call though, so we can afford to raise in cast and calls. I am wondering if the best way to solve this problem would be to have a @before_compile callback that checks if you defined any of the callbacks with a different arity while, at the same time, did not define one with the proper arity. -- 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/CAGnRm4JqC6rzBUYJHd9ij%3DQRH9-mPNDG1qGk1hTMZ6r331iZKA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
