01:28 japhb joined 02:06 amuck_ joined 03:09 amuck joined 04:13 particle1 joined 04:26 eternaleye joined 05:00 amuck joined 05:03 amuck_ joined 10:31 kid51 joined
kid51 kid51's report 10:45
* Have returned to NYC and $job (hence, only available for pre-posting)
* I have 3 patches lined up for application after the July 21 deprecation point:
* trac.parrot.org/parrot/ticket/108
* trac.parrot.org/parrot/ticket/440
* trac.parrot.org/parrot/ticket/490
* There are two other tickets which I would really like to nail down before the July release, but will need active feedback from certain core committers:
* trac.parrot.org/parrot/ticket/786: auto::gettext broken on Darwin
* I now know that this is more than just extraneous warnings during Configure.pl; gettext is not being detected
* need feedback from particle (whose commit last year caused the breakage) on what original reason for change was and how we can work around it, given that code in that region of config/auto/gettext.pm has undergone subsequent refactoring
* trac.parrot.org/parrot/ticket/797: eliminate need to expand Makefile variables in parrot_config and other extrrnal programs
* Am approaching this a little bit at a time; see TT. But suspect that the right thing to do is to banish ALL conditional determination of configuration values in Makefile, as the results of such determinations are not available (via lib/Parrot/Config/Generated.pm, config_lib.pasm) to other programs. Will be seeking feedback from jorwitz, allison and doughera.
* Am eagerly awaiting pmichaud's post on 'make install' issues, promised at YAPC, as that will affect what I and wayland have to work on
EOR
13:01 Whiteknight joined 13:36 pmichaud joined 14:38 davidfetter joined 15:41 rdice joined 16:03 einstein joined
cotto # What I did: 16:18
* YAPC! - many productive discussions, all the important ones being captured elsewhere
* lots of pmc_pct hacking - class_init looks like it's being generated correctly now
- also got some cleanup work done while stuck at the airport, PIT++ for having free wireless
- however...
* bacek had an interesting suggestion that could make pmcc obselete
- instead of working on pmcc, get an ops compiler working
- once that's in place, we'll have most of the tools we'll need to implement PMCs in pure PIR/nqp/etc without needing a specialized compiler
- for now, I've put pmcc on hold
- the ops roadmap is:
+ Dig through the ops2c code, figure out what all the compiler will need to do. (YOU ARE HERE)
+ Make a pct-based compiler for ops that emits the same C code that ops2c does now.
+ Specify enough of L1 to write the ops in it (either directly or in something that compiles to L1).
+ Make PCT capable of transforming L1 into C.
+ Extend the ops compiler to accept other languages (L1, PIR, nqp, bf, INTERCAL, etc).
+ Reimplement ops in terms of L1 (or whatever langauge makes sense). 16:19
* I started trying to rewrite Hash in nqp, started a wiki page to document what's needed to make it work.
- There are some issues which will be tricky to solve (typing, struct access, struct definition).
- Some things may be easier in nqp (methods on STRINGs, all memory management going through the GC, string/int conversion).
- I'm not convinced that nqp is the best language for this job.
# What I hope to do and how many tuits I expect to have:
* I'll start figuring out the subtleties of ops2c and friends.
* I'll also be looking at callgrind's output formatting with the goal of making Parrot spit out something similar.
* My tuit outlook is good and I expect to get some stub code committed before the next #ps.
# What could block my progress:
* There are no external blockers for what I expect to accomplish.
eor 16:20
16:40 jonathan joined
jonathan Pre-pasting report... 16:49
This week...
* Got back from holiday
* Mostly caught up on reading the Perl 6 spec diffs from while I was away
* Started refactoring traits handling to be more in line with latest spec changes, to help more towards my ongoing Hague Grant.
* Had some useful discussions with Larry on traits and MMD, which resulted in some clarifications to S12, some of which lay down in the spec stuff I've been assuming up until now. I had a happy (but now have gotta go work out how to deal with some of the things that it's clarified need to happen).
* subset types without a where now work, and you can specify literals in signatures and have those work too 16:50
* Various other fixes and closing up tickets that are already resolved...between pmichaud++ and I we now have the queue back under 400 tickets...which is still a load.
In the coming week...
* Much more work on traits
* Continuing to work on more bits of D1 of my dispatch refactoring grant
* Probably a Rakudo day somewhere, which given the size of the RT queue will probably go on trying to reduce that a bit
* Need to work out what talks to submit at YAPC::Asia, Italian Perl Workshop and possibly Baltic Perl Workshop too.
Blockers
* Waiting on PCC refactors
* Need to discuss Parrot's MultiSub PMC a little.
.end
(will write to list aobut the Parrot MultiSub stuff though, it's probably better done there).
moderator New proposed #parrotsketch protocol: trac.parrot.org/parrot/wiki/Propos...chProtocol | Please prepost reports by 1800 UTC. 16:50
smash joined 16:51 NotFound joined 16:59 moritz joined
moderator New proposed #parrotsketch protocol: trac.parrot.org/parrot/wiki/Propos...chProtocol | Please prepost reports by 1800 UTC. | Reports can be seen on irclog.perlgeek.de/parrotsketch/today
moderator New proposed #parrotsketch protocol: trac.parrot.org/parrot/wiki/Propos...chProtocol | Please prepost reports by 1800 UTC. | Logs: tinyurl.com/parrotsketch 17:01
17:09 Coke joined 17:10 mikehh joined
Whiteknight #Last 2 Weeks 17:12
- YAPC::NA
- Found some problems with threading, and helped Infinoid++ fix some related leaks.
- Have met some new hackers interested in working on threading, so that may become a group project soon
- Working on IO refactors in the io_cleanups branch
- io_cleanups is stalled temporarily while we better integrate the new Pipe type
- Coke++ started a branch to convert Contexts to a PMC type
- I'm working on that now, give 50% chance that the branch will succeed.
- Finding lots of places where contexts need to be cleaned up and better encapsulated.
- Planning out a new GC core based on the VCGC design. Been playing with prototype code locally for that
- Laying final ground work for AIO, which I hope to start soon (pending io_cleanups branch)
- Planning to fix the PMC subclassability problem, thanks to Allison++. See TT #789
- Lots of talking and speculating about L1, becoming more convinced about it's benefits
- Blogging about and answering questions about L1
- Blogging like a madman to try and increase interest among new users post-YAPC. Have gotten good feedback 17:13
- Meeting lots of new hackers, answering questions, and applying patches.
#This Week
- Continuing context PMC work, will know by midweek if branch will succeed as-is or if we need an intermediate cleanup step first
- Getting io_cleanups branch fixed and merged to trunk.
- Starting on AIO
#Blocking on
- Nothing
EOR
Coke report coke { 17:24
done {
item partcl.blogspot.com/2009/06/improve...-mode.html
item started context_pmc branch (to convert contexts over to PMCs)
}
todo {
item work with whiteknight on context_pmc branch.
item
}
blockers {
item anything marked as lang=tcl in trac.
item anything at code.google.com/p/partcl/wiki/ParrotIssues
item the fact that PIR PMCs cannot do everything C PMCs can.
} 17:25
moritz - parrot: no work done 17:28
- rakudo
+ implemented basics of series (infix:<...>) and eqv operators
+ usual testing stuff 17:29
+ blogging about Perl 6 and Rakudo
:wq
oh, one thing I forgot: I compiled parrot with clang+llvm, it now works --without-gmp
:wq!
NotFound * Added function mem_sys_strdup and replace usages of str_dup with it. 17:43
* Fixed some imcc segfaults.
* Fixed some imcc memory leaks with filenames.
* Working in TT #767, multiple .local with same name. Emitting a imcc warining for a now.
EOR
17:43 allison joined 17:53 Util joined
Util # Done: 17:54
* Attended Day 1 of the Parrot VMW, and whispered about Perl 6 shinyness to my neighbors.
* Found that Parrot's substr does not implement negative length (Perl 5 does). Discussed with Whiteknight.
* Participated in Parrot Implementors BOF. 17:55
* Discussed calling conventions issues with pmichaud and chromatic.
* Recovered from YAPC.
# Plan for the week (or so):
* Write ticket for negative-length-substr.
* Study up on Parrot's calling conventions, in case I can be of help.
* Catch up writing tickets for issues found 3 weeks ago.
* Close pbc_to_exe ticket, with notes on how to patch further when future compilers need similar coddling.
- Well, chromatic closed it. I will update and re-close.
* Dust off my tinkertoy P5/PPI-based P5-to-P6 translator, add pointers to other implementations, and give it a home on GitHub.
# Blockers:
* perl6-examples/shootout stalled, due to branch-of-a-fork issues. Low priority, unlikely this week.
17:55 jhorwitz joined
Util * Minimal tuits through the weekend. 17:56
.end
jhorwitz last week: at YAPC. helped w/ some installs of mod_parrot/mod_perl6. 17:57
refactored mod_parrot configuration system to be less kludgy
this week: working on PDD10 for the foreseeable future
EOR 17:58
pmichaud Pm reports: 18:01
What I did (since 06-16-2009):
* Released Rakudo #18 ("Pittsburgh")
* Rakudo now passing 11,515 spectests (-20 since two weeks ago)
* Rakudo is failing 78 tests (mostly related to -G bugs)
* Just got back yesterday from PVMW+YAPC+vacation
* Parrot Virtual Machine Workshop was _very_ successful
* Full blog posts later tonight
* Fixed a bug in unicode upcase when ICU not present
* Updated Rakudo to be able to build from non-svn Parrot builds
* Rakudo can now define operators in Perl 6 (settings)
What I'm doing this week:
* Blogging and catching up on PVMW+YAPC tasks
* Rakudo day 1 (today): cleaning up Rakudo tickets in RT queue
* Rakudo day 2 (???) : container rw handling, BEGIN blocks
* Provoking and responding Parrot install and build tree issues 18:02
* Solidifying funding for grants, travel
What I'm blocking on:
* Parrot -G bugs / memory corruption
* Cleaner mechanism for building from dynops/dynpmcs
* Installed pbc_to_exe still relies on build tree
* Various perl6-tagged tickets in Trac
q1q
eor
18:04 amuck_ joined
allison - Finished editing and typesetting the book. Submitted it to the printer. Checked the updated book back into trunk. 18:07
- Started working on eliminating the final few build-directory dependencies in the compiler utilities.
EOR
18:13 darbelo joined
darbelo .report decnum-dynpmcs :GSoC 18:17
* No longer sick!
* Put the PCT test converter on hold.
* Bashed together a perl script to avoid getting delayed.
* We have tests! We fail tests! Started work on getting them to pass.
* We are apparently miss-rounding on some cases. Need to investigate more. 18:18
* Changed all numeric getters/setters to return/accpet INTVAL.
* Re-thinking the way we throw exceptions. It might need some corrective surgery.
* I am forgeting something else for sure.
.end
18:20 chromatic joined
chromatic I fixed some bugs. 18:20
I closed some tickets.
We had a nice retrospective at YAPC.
cotto and I discussed how to make a profiling core. 18:21
This week I'll work on that, specifically refactoring runcores to make them easier to plug and play.
I'm blocking on fixing the Context memory leaks until some sort of context/invocation cleanup lands in trunk.
18:24 amuck_ joined
japhb Done: Start of work on OpenGL::Math, to make a useful case study for more HLL-to-parrot calling convention issues. Todo: Continue that. Blocking on: Found problem with sub-namespaces (so when you 'use OpenGL::Math:from<parrot>;', you aren't able to instantiate OpenGL::Math::Vec4 (and adding double colon at the front (::OpenGL::Math::Vec4) just causes fail). Tene knows about this and is thinking about it. 18:30
cotto HELLO 18:31
moritz oh hai
japhb o/
allison hello
jhorwitz hello
smash greetings
darbelo hola 18:32
Util hello
pmichaud say "\\c[104,101,108,108,111]";
NotFound hola 18:34
jonathan hi
jhorwitz pmichaud++ # hello golf
jonathan golf? It was more chars than anyone elses!
cotto more like flog
jhorwitz true
18:34 Whiteknight joined
moritz who's master of ceremonies today? 18:35
allison I guess the first point of order is the changed procedure.
It looks like everyone preposted their reports.
Did we miss anyone?
chromatic Sounds like no. 18:36
What's our vision for the 1.4 release?
Whiteknight ENOVISION 18:37
allison "integration, interoperate, embed"
chromatic What are the milestones to work on with regard to that?
allison That is, fix the install problems.
Whiteknight hll interoperability got bumped from 1.3 I think
jhorwitz PDD10, for one.
allison Make it possible to load foreign HLL libraries. 18:38
And the extending/embedding interface.
Whiteknight what do we mean here by "integration"?
chromatic Okay, do we have a list of install problems and the approach on the wiki somewhere?
pmichaud install problems have been discussed on the trac tickets and mailing list, primarily.
I don't know if there's a wiki page yet. I have some suggestions but need a couple of hours to type them up. I can briefly summarize here with "parrot's build process should create something that looks a lot more like the installation" 18:39
chromatic Would a wiki page help? I know I could take on a couple of small pieces if I had some guidance.
pmichaud I'll be happy to contribute to a wiki page. 18:40
Whiteknight a wiki page would help
allison We have had several email messages on the subject.
pmichaud we had some good discussions about this at pvmw and later at yapc (more)
Whiteknight do we have anybody with knowhow and tuits available to focus on installation issues?
allison In one I suggested changing the directory structure of the repository to match the install.
pmichaud allison: at pvmw we suggested an intermediate step -- namely, have the result of "make" create something that looks like an install
in particular, that would be the version that gets used for testing. 18:41
allison a, build/ directory, perhaps?
pmichaud could be that
chromatic Let's not get into technical solutions here; just project management and priority and resource allocation.
allison did anyone take notes at the pmvw/yapc discussions? 18:42
pvmw
pmichaud I have some notes -- I'm short of tuits for writing them up until later today
allison later today is good
or, dump the rough notes in a wiki for others to clean up
chromatic If they're on the wiki, can we collectively agree to work on those in the next week?
pmichaud knowing that there's general agreement on "refactor parrot build to look more like install" is a big help. 18:43
allison I'll help
smash (i can help too)
Util kid51 took detailed notes of the YAPC Parrot Implementors BOF.
pmichaud I have pictures from that BOF, too.
allison excellent 18:44
pmichaud (the BOF didn't discuss install directly, fwiw)
japhb Util: url?
Util japhb: I don't know if he has posted them yet. 18:45
japhb Util: ah
chromatic Is installation our top priority?
pmichaud It needs to be, yes.
allison yes
well, that needs clarification 18:46
fixing the problems that prevent building tcl/rakudo from parrot packages is a top priority
Whiteknight do we have a concise list of such problems?
smash which packages ?
allison that doesn't include every install feature/fix we might want to make 18:47
japhb And you also said that foreign HLL libraries was high on the list. How high? #2?
allison so we can focus in on the critical ones)
japhb: yes #2
pmichaud I will make a list of problems. But #1 on the list is that it's currently very difficult to build dynpmcs and dynops
allison the embedding interface is #3
pmichaud: but it's possible
cotto smash, basically they need to be able to build from an installed parrot without any dependencies on the build tree
pmichaud and I have fundamental disagreement with the idea of "parrot should generate rakudo's makefile"
chromatic To summarize then. 18:48
allison pmichaud: impossible problems are a higher priority than "difficult"
chromatic pmichaud will create a wiki page listing the problems, focusing on the Rakudo/Tcl blockers.
pmichaud allison: at present I'm not able to build a testable version of rakudo from an installed parrot.
chromatic We've collectively agreed to address those problems as our top priority.
Objections?
pmichaud I've followed the tcl template about as far as I can go.
smash pmichaud: rakudo should be generating it's own makefile 18:49
allison pmichaud: Parrot doesn't build the makefiles, it just provides a utility to help. But there's no reason languages shouldn't write their own makefile processing.
pmichaud smash: I agree. But the steps required to build those makefiles (especially the dynpmc and dynops portion) is particularly hairy.
and requires a lot of maintenance and copy-paste from the language maintainer.
allison pmichaud: think of it like the language shell generators, use them when needed, and not when unnecessary.
pmichaud allison: I do think of it that way. My points remain. 18:50
allison I have some comments here, basically in agreement with pmichaud, and with suggestions for how to move forward. In the new meeting format, should we have this discussion here or on #parrot? 18:51
chromatic #parrot
allison Okay, I'll hang around there and continue this after #parrotsketch.
pmichaud Same.
chromatic Second priority: loading foreign HLL libraries.
japhb Who is interested in working on the foreign HLL library problem besides Tene and I?
chromatic Do we have a page listing open issues and design notes? 18:52
japhb trac.parrot.org/parrot/wiki/HllInteroperability
IS that what you meant?
It's a little out of date (doesn't include the sub-namespace issue)
chromatic Who can update it? 18:53
japhb Assuming edit rights, Tene or I.
chromatic Okay, please do.
18:53 amuck_ joined
Whiteknight japhb: what kind of help do you need? 18:54
sign me up as a willing participant
japhb Whiteknight: some of it is design ... some of it is testing to figure out what we haven't designed yet (the main purpose of OpenGL::Math). And then there's some of just
coding the design up for each HLL's part of the interface 18:55
(In other words, making each HLL keep up its end of the bargain we're designing)
chromatic japhb, can you update the page sometime today?
japhb chromatic: yes
chromatic Excellent, thank you.
Whiteknight japhb++
chromatic Priority #3: extension/embedding API.
Do we have a page for this? 18:56
Do we have a jhorwitz? 18:57
jhorwitz here
chromatic Were you working on this?
jhorwitz sorry, have another call in a minute
yes
chromatic Okay, let's move on then. 18:58
pmichaud, you had a question.
pmichaud Whiteknight answered it earlier, but I have a new question.
Or perhaps a comment.
At any rate -- Parrot seems to have become much less stable for Rakudo of late.
See, for example, nopaste.snit.ch/17066, which is today's daily spectest run. 18:59
chromatic Can we bisect that to a likely range of Parrot commits?
pmichaud I suspect this one is a pbc_to_exe issue. masak++ noticed something similar as well.
In *this* particular case, Rakudo was being run from the 1.3.0 copy of Parrot. 19:00
It's entirely possible that a local Rakudo change triggered the issue (more)
but notice particularly how many strings are being corrupted, such that "Int' is becoming 'Inu', 'Hash' is becoming 'Hasi', 'Num' becomes 'Nun', etc. 19:01
spinclad string++
Whiteknight that's weird and unpleasant
Coke ~~, belatedly
pmichaud I noticed this same problem a week or so ago when I started adding "rw" properties to variable containers.
i.e., simply attaching the property caused strings to be corrupted
allison so it could be a problem with properties? 19:02
pmichaud potentially.
chromatic That's likelier than GC.
pmichaud The problems do disappear when parrot is run with the -G flag, though.
allison properties are largely unused and only lightly tested
Whiteknight yeah, the GC is bulletproof
NotFound I remember a similar looking problems with strings months ago, don't remember well, maybe imcc related
Whiteknight so we need to add more tests for properties? 19:03
chromatic If you have a small test case in PIR, Whiteknight and I can tackle it.
pmichaud it's almost impossible to produce "small test cases in PIR" that tickle these bugs.
Whiteknight then get us a big PIR case and I'll narrow it down 19:04
never met the problem I couldn't solve with a little elbow grease and OCD
19:04 jevin joined
pmichaud Whiteknight: will do. 19:05
Whiteknight thanks
pmichaud More generally I just wanted to note that somewhere since March we've begun losing our "stable platform for HLL implementors"
chromatic More tests needed!
pmichaud somewhere in contexts, strings, and imcc there's something that appears to be corrupting memory. 19:06
allison pmichaud: remember, that stability is the "supported" releases, not the monthlies
spinclad .o( 'rw' property makes ++typename ? )
pmichaud allison: if the problem isn't fixed in the next 3 weeks, it will be a problem in the supported release.
Coke allison: yes, but if there are bugs now, they're going to be in 1.4
allison so let's get it fixed now :)
Coke I'd also like to second pmichaud's point that it's not always possible to reproduce the bugs with a small amount of pir. 19:07
(esp when we use dynops and dynpmcs)
pmichaud I guess what I'm saying is that resolving this issue feels like it ought to be a priority 1.5 or something like that.
moritz in the perl 6 test suite I noticed that real world apps and test cases test very different things, usually
chromatic I'm happy to make it a top priority.
moritz maybe somebody volunteers to write something bigger for the parrot test suite? 19:08
japhb moritz: QUITE.
Coke one of the "install" problems that tcl is facing is that pbc_to_c fails for the installed parrot. need that.
pmichaud I'm currently running rakudo against parrot trunk to see what errors crop up.
(so far there are several)
moritz not geared towards one or two features, but using many, and make them interact in a typical way
allison Coke: yes, that's a big one
pmichaud anyway, that's all I had on that point. I have another comment/question, though. 19:09
spinclad moritz: check in november, web.pm, etc as test suites?
allison Coke: afaik, that's still TT #495
Coke I don't think checking in those to parrot is a good idea, necessarily.
moritz spinclad: that might be a bit too big, and hard to keep up to date 19:10
Coke I think that having smoke tests of HLL projects feed back to parrot is a good idea, though.
chromatic Maybe we should add a milestone to improve our test coverage.
allison we don't necessarily need all tests checked into the repository, we could have an external "application test"
Coke pmichaud: one thing that would be helpful is bisecting to see if you can show a parrot revision introduced a bug (with a single revision of rakudo) 19:11
japhb moritz: perhaps some tests that push the boundaries of sanity? Like pushing recursion limits (but not in theory breaking them), or creating and destroying millions of GC'able objects (but in theory only using a relatively small pool of "active" objects), and so on?
Coke I know that's not perfect, since your parrot requirement changes, but that's a good task for someone with tuits that doesn't require a lot of brainpower.
pmichaud Coke: that's what is really nasty/pernicious about the current situation. Rakudo has been using the 1.3.0 release of Parrot since it came out.
moritz japhb: maybe. I have no really good ideas, just wanted to throw in one point of data/experience
pmichaud Coke: i.e., all Rakudo testing since 06-16 has been against the 1.3.0 release. 19:12
Coke and sometime since 06-16, you've started getting these errors?
pmichaud Coke: Yes.
actually, that's not precise
we were seeing some errors like these on 06-16, but the number and frequency of such reports is increasing
moritz I've seen some parrot backtraces in rakudo's spectest before parrot's 1.3.0 release
pmichaud correct. 19:13
part of the problem with bisecting parrot before 1.3.0 is that there was a longish period of time where Parrot was effectively running with gc disabled
so we don't really know where problems were introduced
Coke pmichaud: check against the last parrot before it was disabled and see if it's there.
pmichaud Coke: by "longish period of time" I mean six weeks. 19:14
Coke ok.
pmichaud There's no way that present-day rakudo will build against an eight-week-old Parrot.
Coke no, but you were getting failures with older rakudos, yes?
pmichaud and, of course, the Rakudo that existed eight-weeks-ago wasn't demonstrating the bugs.
chromatic Shall we try the PIR test case approach and see what happens and move on from there?
Coke ok.
Whiteknight pmichaud: what do you mean gc was disabled?
Coke Whiteknight: it wasn't running. 19:15
chromatic flipped a comparison somewhere, I think.
spinclad bisect on parrots with gc reenabled...
chromatic r39215 was buggy.
japhb spinclad: you mean, bisect but always apply the gc reenable patch?
chromatic Let's move this discussion to #parrot if necessary to continue.
spinclad yes
chromatic pmichaud, you had another question. 19:16
pmichaud Perhaps this comes later in this meeting, but when/where do we attach priority and resources to the items in trac.parrot.org/parrot/report/16 ?
so far they seem to be very starved. 19:17
(also, somehow TT #389 was assigned to me, but I'm not the person who should have ownership of that ticket.)
19:17 Tene joined
allison pmichaud: looks like one for me 19:17
will change
chromatic Any discussion about priorities there? 19:18
Other than "Please fix my language"? 19:19
pmichaud At least for "perl6", the issue is not "Please fix my language" but rather "Parrot has a demonstrable and repeatable bug that is causing perl6 to fail. Please fix it." 19:20
chromatic Noted.
Any other questions?
pmichaud I'm guessing the answer to my previous question is "fix it yourself, or suffer starvation"? 19:21
allison I want to say "core developers commit to review that report regularly" 19:22
I will, at least
chromatic Me too.
Whiteknight ditto
japhb Question: Should there be any particular settings of the TT fields to indicate issues that affect the cross-HLL system?
NotFound Can TT #661 be closed? Last time something said it was pending perl6 testing in windows, if I remenber well. 19:23
japhb (Because I'm probably going to be converting some of our collective problem knowledge to tickets over the next couple days)
chromatic There may be a way to write a report which exposes those, japhb.
Coke (cross HLL) selecting a language should be a multi-select, not a single-select. 19:24
Tene Coke: what?
japhb chromatic: sure ... just wondering if we need to add a "cross-hll" entry to the language dropdown, perhaps in concert with Component: library?
chromatic Seems useful. 19:25
Tene ah, trac
nm
NotFound If not, please someonw write on the ticket about what is blocking in perl6.
Util Coke: s/single/multi/ == Schema change; very non-trivial
spinclad language: cross-HLL? (add a menu entry?)
Coke Util: trac sucks.
allison japhb: I'll add one
japhb allison: thanks.
chromatic Any other questions?
allison Coke: but better than the alternatives :) 19:26
Coke allison: respectfully disagree.
which reminds me, we have about 300 RT tickets to still close out/transfer.
NotFound Coke: 298 last time I checked
Whiteknight I'm sure many of those are so vague and unfixable that they can just be closed 19:27
chromatic Let's call it a day then.
Coke ~~
19:27 Coke left
chromatic When you update the Wiki page with tasks and analysis, please update the topic list in #parrot. 19:28
NotFound Whiteknight: agree
chromatic for our priorities anyway
19:29 Util left 19:30 chromatic left 19:40 NotFound left 19:41 darbelo left 19:52 PacoLinux joined 20:13 jonathan left 20:48 moritz left 21:10 amuck_ joined 21:11 Whiteknight joined 21:39 amuck__ joined 23:14 amuck joined

Powered by Cro and the Raku® Programming Language.

Please report any issues / comments / feature requests as an issue on App::Raku::Log.

Thank you!