On Sun, 16 Jul 2017 23:49:55 -0700, j...@durchholz.org wrote: > 6) If somebody writes his own module in a different location but with > a > matching name (e.g. they might be writing a wrapper, or an emulator), > then these files will be filtered as well. >
The filenames end in .nqp. A Perl 6 users will be hugely unlikely to create such files. > Maybe it's smarter to have a function annotation (i.e. a trait, I > believe) for "don't include this in backtraces"; this would deal with > all problems except (2). The code in question is implemented in NQP, which doesn't have a generalized traits mechanism. As to disabling the filtering mechanism, that's entirely possible today with --ll-exception. The code in question is producing backtraces that will contain things relevant to a Perl 6 user, using these heuristics to filter out implementation guts that will almost certainly always be a distraction. Is it beautiful code? No. It's been a pretty good heuristic to date, however.