Sanko Robinson
Sanko Robinson
@DrHyde, you could cache the built perls with Github's own [actions/cache](https://github.com/actions/cache). It's what I did for https://github.com/sanko/Affix.pm/blob/main/.github/workflows/ci.yaml. The majority of that workflow is there to work around perlbrew being incompatible...
MetaCPAN has fully tipped over. I was checking to see if it caught up to an upload I made after PAUSE came back online and the recent page now returns...
You're free to fork, repair, and submit a PR.
Pull requests with tests welcome.
Right now, it looks like another upstream bug in perl itself. Simply accessing the value inside Readonly::Clone(...) 'fixes' it. I'm trying to narrow it down to a minimal example that...
Take two! Got it down to a generic example that doesn't use Readonly. ``` use strict; use warnings; use Tie::Hash; use Tie::Scalar; use Data::Dump; $|++; sub _debug { warn ref...
Reported as https://rt.perl.org/Ticket/Display.html?id=128588. Unfortunately, tie is kinda the redheaded stepchild of perl. I've had trouble with it ever since I took over Readonly and would rather throw all that classic...
Have you tried the drop-in replacement for Readonly I sent you about a month ago? https://metacpan.org/pod/ReadonlyX It isn't encumbered by tie.
Exposed by a test regression but the problem may be `Internals::SvREADONLY($)` not seeing normal constants (strings, numbers, etc) as read only on some builds of perl. Hadn't even tracked it...