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

Larry:

• clarified that object identity from WHICH may not be a mundane value type
• instead object id's are of type ObjAt to avoid type name collisions.
• rewrote misleading description of "thunk"
• made some clarifications of the desired semantics of buffers
• Buf is primarily a role for dealing compact, unsigned integer arrays in a stringy way
• but a Buf may be instantiated with other numeric types as well.
• removed bogus mentions of Buf8, Buf16, Buf32; only the native buf types are sized that way
• STD now actually parses the insides of tr/// and carps about malformed ranges
• labels are now stored symbolically as constants rather than types
• so no coercion routine is added for the name, so it doesn't collide with the function namespace
• labels are now constants with a unique label type to prevent confusion with ordinary constants
• module subcompilation now reports the name of the file it's compiling
• improved various error messages regarding foreach, !!op, $!{}, EOF, and missing punctuation after blocks

Allison:

• worked on line number reporting in HLLs
• no ticket to go on, no good examples
• didn't make much progress, but didn't have much time
• sounds like Christoph and chromatic are working on it
• might look at TT #389

c:

• you're welcome to it!
• let me know if you have questions; it's close

Allison:

• no travel plans for the next couple of months
• should have a lot more Parrot time
• probably time to consider another big project
• probably GC related

Patrick:

• updated the progress graph last night
• up to date as of yesterday
• Rakudo's passing over 30,000 tests, which is great

Jerry:

• we have 27 mentors signed up for GSoC
• a dozen student proposals have come in
• the admission period ends Friday, so I expect at least a handful more
• looks like a good year for proposals
• trying to keep on track of Rakudo development
• trying to be a go-between for Rakudo and Parrot
• seems like it's helping Rakudo as Parrot addresses issues that come up

c:

• Vasily and I fixed the Rakudo performance regression
• we're going to experiment with immutable strings in a branch
• expect some notable performance improvements there
• also worked on the plan to fix line number reporting
• need a test harness to help identify problems and avoid regressions
• learned my lesson last time I worked on that....

Larry:

• I cringe every time I hear "line numbers"
• I like what Clang does about highlighting the arguments to functions
• it'd be nice if we can do similar

c:

• that'd require more changes to Parrot, but it's doable

Larry:

• I just want people to bear it in mind

Allison:

• there's no reason we can't have richer annotations
• our first step is making sure the information we provide them (or they ask for) is accurate
• is it time to have another big development meeting for Parrot?
• the release is coming up

Jerry:

• sounds good