Ovid
@leonerd wrote: > 1. Modules like `Data::Deep`, `Test::Deep`, or the `is_deeply()` function of `Test::More`, which will want to recursively inspect the fields of objects in order to compare if they...
I agree with @happy-barney here. The way subtests were originally designed (er, hacked into the mess that was the old test harness) is that test output would be line-based and...
I would suggest that the less dependencies we have on order, the more robust p5-mop is likely to be. We don't care what order subs/methods are declared, why should we...
I'm definitely in favor of this. I've already been bitten by it as it seems natural to allow this.
Yes, we have multiple projects in a single database. Having a `--purge` option would be nice with revert, though I can see danger there :) But you're right, it's all...
> In production, when dollars and business continuity are on the line, it's not enough to encourage best-practice workflows. With large-scale projects and multiple developers working on multiple versions of...
Per jnthn's request, an example without multis or subsets: ``` role Alpha { method foo() { return "Alpha::foo" } } role Beta does Alpha { method foo() { return "Beta::foo"...
@colomon But that's OK. In typical multi dispatch the more specific type wins. Let's say I have this: ``` class Mammal { ... } class Cat is Mammal { ......
Yes, this does look like a duplicate of https://github.com/Perl/perl5/issues/20890. Sorry for that.
@brendanjones Done!