Toby Inkster

I've been getting "No MYMETA file is found after configure. Your toolchain is too old?" running `cpanm` on Perl 5.6.1, 5.6.2, and 5.8.0. (5.8.1+ is fine.)

Oooh, additional information. `should_fail` is called all over the test suite, so I was curious why it was only this particular call that was dying. Line 44 performs the 100th...

I can reproduce with this: ``` use strict; use warnings FATAL => 'all'; use Test::More; sub bar { goto \&Test::More::ok } bar(1) for 1..101; done_testing(); ```

Further, `Test::More::ok` has a signature on cperl, though http://perl11.org/cperl/#Changed-calls-to-signatures seems to suggest that using `goto` would be the *correct* way to do a tail call to it.

How would you recommend I disable these warnings then? ``` BEGIN { 'warnings'->unimport('shadow') if "$^V" =~ /c$/; }; ``` At the top of every file affected (because it needs to...

Note that I'm not saying `use warnings` or `-w` shouldn't be able to enable these warnings. But right now, they happen without opting into them at all.

It doesn't detect problems though; it detects situations which might result in problems. Like how if you were parsing HTML and somehow ended up with a variable containing what you...

To summarize my feelings on this warning, because I don't think I have necessarily expressed my self clearly. my $var = "5"; # perhaps because of broken HTML scraping say...

I've been trying to get the test suite for my own distribution, Type::Tiny, passing on cperl. The version on github does now pass, albeit with these warnings and needing to...

The Bool type is defined by Moose as allowing undef, the empty string, 0, or 1. Although it's undocumented, it silently allows overloaded objects too, but uses their stringification instead...