03:07 TimToady joined 04:58 sorear joined 10:14 masak joined 18:30 diakopter joined
diakopter sketchy 18:55
moritz_ aye
masak o/ 18:56
still a few minutes left.
colomon t minus 4
jnthn o/ 19:00
moritz_ ¸o
jnthn
.oO( role Call; )
masak :P
moritz_ that's me hanging over the chair because I ate too much for dinner
jnthn Sorry I wasn't about last week - the wilderness has no internets.
spinclad \\o 19:01
moritz_ np
colomon o/
jnthn I've nothing much to report - I comitted a couple of minor fixes, but mostly spent my vacation being, well, on vacation. :-)
colomon I did a bunch of Numeric stuff: sqrt, log, sin, comparison operators (mostly for Real) so far. 19:02
jnthn OK, sounds good.
moritz_ anythin' you're blockin' on?
colomon Plus Sop, cmp for Pairs, and fixing ^$n so it makes $n be a number.
I don't think so. In particular, getting sin done means that all the trig functions are just a matter of time.
moritz_ that's good news 19:03
jnthn colomon++
Sounds like good progress both for Rakudo and your grant.
moritz_ indeed colomon++
colomon I'
I'm assuming I can't do TrigBase $base = CALLER::<$?TRIGBASE> yet?
moritz_ nope
jnthn No
moritz_ pseudo packages NYI
jnthn Will you block on that?
colomon I don' think that's really a blocker.
jnthn OK.
colomon just a detail that can't be implemented yet.
jnthn pseudo packages are on the ROADMAP 19:04
moritz_ I applied some patches
lured another contributor into patching tests
masak moritz_++
moritz_ not much progress with match objects...
the problem is that NQP-rx uses vtable calls to populate the Match object 19:05
jnthn Yay, another test hacker. \\o/
masak I don't have much to report either. dry spell with rakudobugs right now. will probably get started on my GSoC grant as soon as I'm done with Moscow+presentation.
a week from now.
moritz_ and for some of them I've only encountered recursions
colomon \\o/
moritz_ between set_pmc_keyed and postcircumfix:<{ }> in Associative 19:06
jnthn moritz_: Yeah, I can see how that could end up happening.
moritz_ jnthn: any good ideas what I can do about it?
jnthn moritz_: Will have to look at the details to see a solution.
moritz_ ok
I'll brush up the branch and push it
I have a hackish workaround
that calls eval_set_pmc_keyed method 19:07
jnthn moritz_: OK, sounds great. I'm not too optimistic about getting time today, but tomorrow after I've given my talk should be better.
moritz_ which I've then implemented in Match
I've got non-quantified named captures working that way
more of a proof-of-concept, nothing to go into rakudo
jnthn *nod*
masak: Off to Moscow this week?
moritz_ that's my report, basically 19:08
masak jnthn: yes. Sunday, ashcloud permitting.
jnthn masak: Yay! And I hope the ashcloud permits.
masak me too.
jnthn masak: Anything you're blocking on or needing in the GSoC run-up? 19:09
masak to complicate matters, I'll be in Värmland the two days prior to that.
jnthn: don't think so. I could round up a bunch of 'serious' RT tickets, if that helps.
but I'm not blocking on the grant yet.
jnthn masak: Having some user perspective on what tickets hurt most is a nice thing. 19:10
moritz_ anybody else got something to report?
if not, i'd like to turn our attention the to the book 19:11
I've added somethiing about comparison operators, and plan to add more about string comparison ops and smart matching
jnthn OK, sounds good.
moritz_ szabgab expressed interest in contributing... let's see how much time he can invest
jnthn I plan to do more book than code in the next couple of weeks. 19:12
moritz_ do we have any priorities for getting it printable?
colomon I probably could have used whatever you wrote, I totally botched the lt, le, gt, etc operators over the weekend. :)
moritz_ :-)
I've set the book title to 'Using Perl 6', and will keep it that way until sombody protests 19:13
jnthn moritz_: The OO and roles chapters are still weak. subs-n-sigs needs a bunch more work.
moritz_: Those are the areas I expect to mostly focus on.
moritz_ ok
also dropping in TODO markers where you feel somethiing is weak is already helpful
jnthn moritz_: Yes, certainly. 19:14
moritz_: It'd be good to grep through for the ones we already have.
(That's for all of us, not just moritz_.)
moritz_ did that last weekend, and eliminated a few of them
masak I'll focus more on the book too, starting next week. I still think we need more chapters, but I'm not sure what more needs explaining.
jnthn To get a feel for other bits that need improving.
masak: I felt more that we need to fill out many of the chapters we already have some more.
moritz_ I'd also like to get some more feedback from chromatic - it has been hard to lay hand on him during the past few days 19:15
masak I still think a poker hand example would be good for explaining subsets.
jnthn: oh, definitely.
jnthn masak: Do you have time to write the code example?
masak jnthn: I think so.
jnthn finds it much easier to write about and explain examples than to come up with them, fwiw.
moritz_ that would be great; others could then chime in and... right
masak jnthn: there's already working code. 19:16
I could put it in the book repo and see what happens. :)
jnthn Go for it. :-)
masak does so
moritz_ bad things, hopefully not, speaks yoda
jnthn A lot to write still we have.
masak why suddenly like this we speak? 19:17
moritz_ of the yoda conditions /me thought
jnthn To get it out of us now so it doesn't end up in the book.
masak :) 19:18
jnthn I probably need to take the time at the weekend to read through the book that we have so far to get a feel for what we have / haven't got. 19:19
As well as writing some bits.
jnthn doesn't have a good feel for the overall state ATM.
moritz_ if you have some gripes about rendering in latex, talk to me
[Coke] (poker hand example) ah, I think I still owe someone code on that.
moritz_ I've hacked up the latex emitter quite a bit 19:20
masak [Coke]: would be nice if you could look at the XXX comment. gist.github.com/244255
moritz_ the only remaining issues I know are side bars
masak [Coke]: if you don't have time, that's cool too.
jnthn Any more bits on book? 19:23
moritz_ don't think so
jnthn OK.
Any more things to discuss on Rakudo * bits?
I notice sorear++ sent in a patch for one of our ROADMAP priority 1 items.
I didn't read pmichaud's feedback yet; I did see things in it that made me uncomfortable 19:24
But the fact that we have a patch that works is a good starting point.
moritz_ aye; pmichaud commented that the ground work was solid, but more polishing required
jnthn Ah, OK, that's promising then. 19:25
moritz_ has high hopes
I plan to assemble a list of most annoying bugs that are my personal favorites for 'fix before R*'
masak are we 'on track' for the priority 1 items? 19:26
moritz_ is a bit worried about lists/arrays
jnthn Ah, also (certainly since the last Rakudo sketch I was at) we also got "lexical classes and roles" marked as complete.
moritz_: Me too - I see in the Perl 6 call pmichaud still expects to have time for those soonish. 19:27
"improved error messages and failure modes" - I'm quite happy we've made big steps forward on our parse time errors here.
I may try and get Perl 6 level backtrace printing done again. 19:28
The problem with that item is that we can always be More Awesome
masak that's not a problem :)
except about us being unable to mark it as finished, of course.
jnthn But I think if we can get mostly-correct runtime errors nailed, then I'd be prepared to say that we're done enough. 19:29
That is, ones that report the line/file in the Perl 6 source.
"lexical variables in regexes" - don't think bkeeler is about ATM to ask; anyone know anything on that?
masak he made patches quite a while ago for those. 19:30
don't know what heppened since, only that they didn't go in.
jnthn OK, since pmichaud++'s last round of feedback?
masak no idea. 19:31
jnthn OK 19:32
colomon is also worried about closures.
spinclad worries about closures -- they're getting pm's attention, working with #parrot -- /me wonders if i could talk with pm
moritz_ spinclad: did you see the discussion on #perl6 today about closures?
jnthn Yeah, those are the two bits that we're currently quite dependent on pmichaud++ for
spinclad moritz_: the start of it, at least, still backlogging 19:33
colomon three bits? lists, closures, and variables in regexes?
moritz_ sounded like he had a plan forward (on closures), at least partially
jnthn colomon: I'm not sure if variables in regexes are currently blocking on another round of feedback or not. 19:34
moritz_: Yes, I believe so.
moritz_ I think on bkeeler's tuits
jnthn OK.
moritz_ (which he announced three weeks ago, or so) 19:35
jnthn OK. So that's most of the priority 1 ROADMAP items discussed. I'd really like it if one more got knocked off before #rs next week. 19:37
Or more than one.
I can probably take at least one of them. :-) 19:38
Do we have any progress on getting the advent calendar examples into some kind of a test sutie?
*suite
1 *** get the Advent examples running again (all) 19:39
I'd really like to know how close we are/aren't.
colomon has anyone done anything at all for that? (he asked, embarrassed....)
jnthn colomon: Not that I'm aware of. 19:40
moritz_ I've gone through some of them 19:41
the first posts don't need any rakudo updates
jnthn moritz_++
moritz_ but I forgot how far I got
jnthn I figure the ones towards the end are likely to get harder. 19:42
moritz_ all issues I've seen were known/ticketed
jnthn Since we covered more advanced stuff later on.
OK, anything else anyone wants to discuss? 19:46
Otherwise, we'll wrap up here and I'll go cook my noms.
moritz_ good nomming
colomon I kind of feel like we could use a Rakudo pep talk. (which I definitely don't have in me.) 19:47
masak for what it's worth, I still think we can put forth something quite good for June. 19:49
jnthn Me too. Rakudo certainly has its weak areas, but it also has a lot of strong ones too. 19:50
colomon woah. I don't think I'd actually conceptualized it before, but I think that's it -- I'm starting to get worried about June.
masak it's mostly a question of packaging and tutorials and examples at this point.
moritz_ sees lots of stuff that should get fixed first 19:51
colomon I'm with moritz_.
jnthn I think that for June, we're certainly not on course to deliver something perfect - but that was never The Plan. If we try to do that we'll never release anything. We're on course to deliver an implementation that covers many of the things that Perl 6 has promised.
Yes, we've got some nasty bugs and rough edges still. 19:52
But we've also fixed a lot of nasty bugs to date.
moritz_ aye
jnthn A lot of things are coming together. There's certainly some very concerning areas, but there's a lot of things that we're doing really quite well. 19:53
colomon I think what has me worried is it appears that many of the remaining nasty bugs are blocking on pmichaud's tuits.
jnthn colomon: Yes, that is certainly a concern.
moritz_ it would be nice to find a way to increase our bus number
jnthn It's my biggest worry too.
diakopter is curious why sorear hasn't spoken up
jnthn I've already picked off many of the eaiser things that would have blocked on pmichaud (like the user defind operators and item assignment) 19:54
spinclad what's the limit on handing the book off? that's the tightest constraint now, maybe
jnthn But the lists bit is, well, rather harder to Just Do.
spinclad: AFAIK, end of the month.
diakopter imho, sorear himself increased the bus number significantly. 19:55
colomon end of May?
jnthn diakopter: I think timezone may be part of it.
diakopter he's in PDT like me I think
jnthn colomon: Aye, thus my mention earlier that I intend to spend more time on book than code in the next while.
diakopter: Physical timezone and actual timezone don't always correlate. ;-)
colomon sorear++ has been doing fantastic things. but they don't seem to be making much of an impact on Rakudo yet. 19:56
jnthn But yes, sorear++ is very much digging into Rakudo.
colomon: They are, and will. I expect once the pollishing is done, the patch for the REPL bits will go in, for example. 19:57
moritz_ colomon: my first 20 patches to rakudo didn't make much of a difference to rakudo, not each on its own
jnthn colomon: And the patches for the first bits of Perl 5 support did also.
colomon sorry, that wasn't meant to be a knock on his patches. 19:58
jnthn colomon: I didn't read it was one, fwiw.
colomon more a remark on how they are stacking up in a corner by themselves instead of becoming part of master.
I don't think that's sorear's fault, either. 19:59
moritz_ it's more lack of patch applier's tuits
jnthn Well, patch reviewer's tuits also.
diakopter my thought on that ("more a remark..") is that sorear should be encouraged to blaze trails notwithstanding patch reviewers' availability
moritz_ +1
spinclad +1 20:00
diakopter (sorry if I'm stating the obvious) :|
diakopter shuts up
colomon +1
spinclad (obvious)++
colomon I just want the rest of us to be able to follow those trails.
masak +1 20:01
jnthn +1, and I'll try to do my part to be reviewing patches from him too
masak I really like how sorear++ has been blazing trails so far.
he's really upsetting the status quo :)
jnthn Yes. The macros work was a big surprise. :-) 20:02
pmichaud hello 20:07
jnthn \\o/
pmichaud: hi!
pmichaud sorry I'm late -- small disaster here.
jnthn pmichaud: :-( 20:08
spinclad \\o/
masak welcome, pmichaud.
jnthn pmichaud: No worries, happy you've made it at all. :-)
colomon o/
spinclad (welcome, glad you made it)
pmichaud (long story short... while installing a new cable so that we can get better cell coverage in the house, I hit a water line)
OOOPS 20:09
jnthn D'oh!
masak sucks in breath
colomon yow!
pmichaud although why the builders stuck a water line mere inches away from an electrical outlet is beyond me.
spinclad hold breath, treads water
pmichaud anyway, closures. I should have closures fixed in the next day.
jnthn
.oO( Quits pmichaud: excess flood )
 20:10
spinclad \\o/
colomon \\o/
jnthn pmichaud++ # yay!
colomon that's huge.
moritz_ wondered for a second if "closures" can be used to close water leaks
pmichaud Fortunately I took a shortcut when working on Parrot lexicals back in 2008 that means that fixing closures will be far easier than if I had done it the right way.
colomon shortcut++
pmichaud essentially, capture_lex and newclosure don't do as much checking as they probably should. They're a bit naive. And the fact that they're naive means I can fix them. :-) 20:11
s/fix them/exploit their naivety to make sure that closures actually work/
although we may have trouble with closures that are also multis
jnthn We'll just call it an "extensible implementation"
pmichaud but I don't think we have many closures that are multis. And it might work out correctly anyway. 20:12
anyway, I'll have closures fixed in the next day or two.
moritz_ we don't? 20:13
jnthn pmichaud: iirc, last time you hit some issues with parametric roles when doing closure fixes. If they come down to your only blocker, but everything else works and the other bugs are fixed, feel free to punt the fixes to those to me.
pmichaud jnthn: I think it's all going to Just Work.
masak \\o/ # closures
pmichaud jnthn: but yes, if I run into problems I'll punt.
colomon do we have good tests for the closure-related bugs?
jnthn pmichaud: OK. And if it Just Works that'll be wonderful. :-)
pmichaud I think it'll just work because PCT is smart enough to recognize when we're using blocks as rvalues :-) 20:14
spinclad (vs ivalues (invoke/immediate))
pmichaud well, it's not only then 20:18
if we have
{ say 'hello'; sub foo() { ... }; say 'xyz'; }
then foo() is not immediate but it's also not being used as an rvalue
(i.e., it's in sink context) 20:19
although it might be a bit tricky because the block is bound to lexical &foo. Anyway, it'll either just work or we'll have to muck around with lexicals just a bit. 20:20
I'm hoping for "just work" (although perhaps sub-optimally for a short bit) 20:21
reading backlog
moritz_ well, anything better than what we have right now is an improvement
spinclad wants to know more but doesn't want to devote #rs to it. could i ask you about back on #p6 after?
pmichaud I call "tautology!" :-)
moritz_ pmichaud: I was quite aware of that :-)
diakopter I call truism! 20:22
pmichaud anyway, my #rs report: I've been working on fixing closures, should have that in the next couple of days. 20:24
things are settling down around the house a bit so that as expected, I should have more time to devote to R* 20:25
I'm currently catching up the spectest-progress.csv file on my notebook
after closures are fixed, I'll work on lists/arrays next 20:26
I'll also see if I can make some better pointers about how interactive mode should work -- the current patch is too brutal on the code generators
EOR 20:27
jnthn will be very relieved to see closures fixed. :-) 20:33
spinclad too
masak oh yes. 20:34
spinclad meeting over? 20:53
masak seemingly. 20:54
spinclad <gavel>
21:02 masak left 21:13 diakopter left
spinclad phenny: tell ash__ (even if thrown away in sink context) ... but pmichaud seemed to have a different point of view on #rs. 23:25
EWORNGWINDOW 23:26

Powered by Cro and the Raku® Programming Language.

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

Thank you!