If we can detect those confidence, it sounds like a good one to me.
*José Valim* www.plataformatec.com.br Skype: jv.ptec Founder and Director of R&D On Mon, Sep 11, 2017 at 5:16 AM, Michał Muskała <[email protected]> wrote: > Hello everybody, > > After watching José's keynote, I had an idea about extending > Exception.blame to enhance even more exceptions. A great candidate is :ets. > Most of the functions raise badarg for different exceptions. The primary > issues once can recognise are: > > - table is private/protected and other process tries to read/write it > - the arguments are actually bad > - wrong type of table for the operation > - value is not present in the table (in lookup_element) > and more. > > It's possible to detect a lot of these conditions more precisely using the > stack trace, arguments and some calls to :ets.info/2. > > As a first step, I think detecting table being private/protected would be > the easiest one and give the most value. > > What do you think about this? > > Michał. > > -- > 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/003ef9cd-3c9e-41ff-aacb-b57c1a35c858%40Spark > <https://groups.google.com/d/msgid/elixir-lang-core/003ef9cd-3c9e-41ff-aacb-b57c1a35c858%40Spark?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CAGnRm4KpoKdOXHHHsM3RZEbhr9udBd5KxsAUukpuCf7-cr%3DkkQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
