Slash Boxes
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

use Perl Log In

Log In

[ Create a new account ]

chromatic (983)

  (email not shown publicly)

Blog Information [] Profile for chr0matic []

Journal of chromatic (983)

Saturday May 01, 2010
07:27 PM

Perl 6 Design Minutes for 28 April 2010

[ #40338 ]

The Perl 6 design team met by phone on 28 April 2010. Larry, Allison, Jerry, Will, and chromatic attended.


  • caught up on a week's worth of backlog
  • made a few spec tweaks
  • discussed them with other people
  • trying to make error messages more awesome in STD
  • working on the ability to parse the insides of character classes
  • STD doesn't like parsing itself recursively there
  • need to iron out a few things
  • enum names can now be variables


  • Debian packages ready to ship to Debian sponsors
  • putting together a list of GC tasks
  • cleaned out the existing page, have the big things listed
  • trying to decide which tasks to do first
  • doing a lot of reading and research
  • my little language project is due on Monday
  • HLLCompiler was enormously useful
  • will start working on the GC stuff next week
  • should also start a fresh pass through the ticket queue
  • added a workaround for the final remaining TT #389 bug
  • Jonathan had a test case


  • tried to focus on getting Rakudo blockers removed


  • spent some time getting Rakudo to work with trunk
  • will need a Rakudo guts hacker for the last part
  • worked on the compact_string revamp branch with Vasily
  • merged now
  • that makes trunk about 12% faster than the 2.3.0 release
  • will work on a few Rakudo profiles once it works with trunk again
  • expect at least a 5% performance improvement there
  • have some other ideas, but won't do them without profiling first
  • came up with a scheme to reduce PBC size by coalescing strings
  • Peter Lobsinger is exploring that
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
More | Login | Reply
Loading... please wait.