Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • From my part, I can say that your bug reports are *very* highly valued, even if they aren't resolved quickly. While from your point it has probably felt like not much was done, Rakudo has taken quite a few steps during January. They have muchly been on adding features than resolving bugs in existing things, though. That's both a good and a bad thing - we're some steps closer to implementing the Perl 6 spec now, but for sure it's not so encouraging for those using and reporting bugs in Rakudo.

    To take some examples of what happened in January: we moved to a new repo, got parametric roles (which also lay the foundation for typed arrays and hashes), junction auto-threading is done, nested classes are further along, the type registry is in place, the handles trait verb does most of what the spec says it should, we're closer to custom dispatchers after a dispatch refactor, there's more compile-time error checking, role composition and multi/proto methods now play nice(r) together...and more.

    After a very feature-focused January, I hope to look more at bugs this month. We need balance, and I'm trying to strike it on my part. Thanks for sticking with us, and please don't feel ignored. Sometimes - and I'm speaking for myself here - there just needs to be space to focus away from the ticket queue a bit and get more of the spec implemented. Otherwise, we'd end up doing a subset of Perl 6 wonderfully - rather than the whole spec releasably. :-)

    Thanks again!

    Jonathan

    • Thanks for the heart-warming comment.

      Thanks for sticking with us, and please don't feel ignored.

      I can assure you I don't feel ignored. I understand and agree with the argument about the features/bugfixes balance. Now that you mention it, much has happened under the hood in Rakudo which will benefit the Perl 6 projects out there -- even though a lot of it looked like regressions in the short run.

      More than anything else, this post was a reminder to myself that targeting Rakudo is a bumpy ride, but that that's part of the original deal. If it weren't, I'd have written