jnthn patrickb: In principle, yes, I can mentor...will have to ponder project ideas a bit. 00:12
patrickb jnthn, samcv, MasterDuke: Thank you for taking the time to think about mentoring and ideas! 00:30
I'm off to bed. Night everyone! 00:44
nine How much time does mentoring need? How much latency is still OK? I'd be interested, just not 100 % sure I have the time. 07:44
As to project ideas, that's much harder. I usually act on my ideas :) The projects I haven't done yet are more on the edge of or even beyond my current abilities, so probably not good for a newbie. 07:46
sena_kun releasable6, status 10:20
releasable6 sena_kun, Next release will happen when it's ready. 1 blocker. 0 out of 508 commits logged
sena_kun, Details: gist.github.com/48a922a744fb4a0105...1d2cbaa861
nine I don't think a bug in Documentable is a real blocker for the release 10:21
sena_kun of course. :)
the current state of things is: 1)we are very ready for moarvm point release; 2)right now I am updating the release branch to be up to date; 3)after moarvm release I am cutting a release ASAP 10:22
lizmat Files=1301, Tests=109805, 210 wallclock secs (28.50 usr 8.04 sys + 2943.37 cusr 241.31 csys = 3221.22 CPU) 10:46
Altai-man_ ++ 10:47
Geth rakudo: e3cbd32c6b | (Elizabeth Mattijsen)++ | src/core.c/Str.pm6
Add Version coercer to Str

This not only allows you to just do `"foo".Version` to get a Version object, this also allows you to use `Version(Str)` in a signature.
11:03
Geth rakudo: 11a8d57f6d | (Elizabeth Mattijsen)++ | src/core.c/Perl.pm6
Save 2 Scalar allocations at each startup

And make the version cache a little more optimised
11:40
nqp/compressed_lex_loc_types_serialization: f7631eb747 | (Timo Paulssen)++ | src/vm/moar/QAST/QASTCompilerMAST.nqp
"Compress" types of locals and lexicals in serialization

  "obj" registers/lexicals are overwhelmingly common,
so leaving their data out is worthwhile.
The result is a 1.85% size reduction of CORE.c.setting
11:54
Altai-man_ phew 12:04
changelog is ready, now $dayjob
lizmat Altai-man_++ 12:08
lizmat Looks like "is built(:bind)" needs some extra work: 13:14
m: role A { has $!a is built(:bind); method TWEAK() { $!a := 42 } }; class B does A { }; dd B.new # yeah, great!
camelia B.new(a => 42)
lizmat m: role A { has $!a is built(:bind) }; class B does A { method TWEAK() { $!a := 42 } }; dd B.new # not so great
camelia Type check failed in binding; expected NQPMu but got Int (42)
in method TWEAK at <tmp> line 1
in block <unit> at <tmp> line 1
lizmat I wonder if it step one causing this issue: 13:15
m: role A { has $!a is built(:bind); method TWEAK() { $!a := 42 } }; class B does A { }; use BUILDPLAN; note BUILDPLAN(B)
camelia class B BUILDPLAN:
0: nqp::bindattr(obj,B,'$!a',:$a) if possible
1: vivify nqp::getattr(obj,B,'$!a') if part of a mixin
2: call obj.TWEAK
lizmat golfed it down to: 13:26
m: role A { has Int $!a }; class B does A { method TWEAK() { $!a := 42 } }; dd B.new
camelia Type check failed in binding; expected NQPMu but got Int (42)
in method TWEAK at <tmp> line 1
in block <unit> at <tmp> line 1
lizmat aka nothing to do with "is built(:bind)" 13:27
I guess if we don't install a container for the attribute, then there's nothing to type check against, and NQPMu is what we get to match against
jnthn ^^^ is that assertion correct ?
m: role A { has Int $!a }; class B does A { method TWEAK() { use nqp; nqp::bind($!a,42) } }; dd B.new # naughty workaround 13:30
camelia B.new
jnthn lizmat: No, that looks wrong (leaking an NQPMu is certainly wrong) 13:33
lizmat jnthn: it happens somewhere in what p6bindassert generates, afaics 13:34
I guess $tcr_reg is not set 13:35
ah no, that's the register that contains the result of the istype I guess 13:36
bisectable6: role A { has Int $!a }; class B does A { method TWEAK() { $!a := 42 } }; dd B.new 13:40
bisectable6 lizmat, Bisecting by exit code (old=2015.12 new=11a8d57). Old exit code: 0
lizmat, bisect log: gist.github.com/cd58c67be7403dcaac...6aaeb17dc2 13:41
lizmat, (2016-11-05) github.com/rakudo/rakudo/commit/94...79aae73698
lizmat yeah, well, that's bogus 13:42
bisectable6: role A { has Int $!a }; class B does A { method a() { $!a := 42 } }; dd B.new.a 13:43
bisectable6 lizmat, Bisecting by output (old=2015.12 new=11a8d57) because on both starting points the exit code is 1
lizmat looks like it has always not worked 13:44
bisectable6 lizmat, bisect log: gist.github.com/84509d65b72d0a3772...603ed47cac
lizmat, (2016-02-18) github.com/rakudo/rakudo/commit/99...4283b48d0a
lizmat yeah, also bogus
github.com/rakudo/rakudo/issues/3436 # jnthn 13:47
afk for a few hours& 14:14
|Tux| Rakudo version 2019.11-510-g11a8d57f6 - MoarVM version 2020.01-17-gefb014f19
csv-ip5xs0.703 - 0.738
csv-ip5xs-206.300 - 6.365
csv-parser21.876 - 23.206
csv-test-xs-200.364 - 0.372
test7.494 - 7.747
test-t1.770 - 1.849
test-t --race0.788 - 0.794
test-t-2029.954 - 29.993
test-t-20 --race8.411 - 8.728
14:23
brrt .tell patrickb I might mentor again, and maybe a followup project is a good idea, but I'd think it best to reach out to the original GSOC student again 14:51
tellable6 brrt, I'll pass your message to patrickb
TreyHarris I got inadvertently tangled up in terminological conventions on p6-u yesterday -- are we generally calling a multi routine with (possibly sub) definitions that can be usefully called without invocant--as in `.say for lines`--`.lines`, `lines`, `lines()`, or something else? 16:30
On docs.raku.org, the hyperlinks make the question less salient than in straight prose 16:31
nine TreyHarris: I don't think I understand your question 16:38
TreyHarris nine: If I want to talk about the notional entity discussed in docs.raku.org/routine/lines -- composed from many definitions that are interparticipating -- do we have a convention how to refer to it, as `.lines` vs `lines()` would be used in discussing many C-family OOP languages? 16:40
[Coke] I don't think there's a standard format for a "routine" that has both method & sub forms. 16:42
TreyHarris Okay. That's fine; I don't mind not having a convention, I just don't want to be not following it if we did have one 16:44
[Coke] Thanks. 16:50
patrickb brrt / samcv: nine asked about the (response) time needed for mentoring. Could you share some experience? 18:05
tellable6 2020-01-21T14:51:30Z #raku-dev <brrt> patrickb I might mentor again, and maybe a followup project is a good idea, but I'd think it best to reach out to the original GSOC student again
patrickb brrt: Recruting last years student again seems like a very smart move to me. Can you try to get in contact with pamplemousse again? 18:06
brrt I'll try 18:08
tellable6 2020-01-21T16:02:09Z #moarvm <nine> brrt: I posted the link yesterday :)
2020-01-21T16:02:35Z #moarvm <nine> brrt: mere minutes before you joined the channel
patrickb brrt++ 18:09
patrickb vrurg: You there? 18:20
vrurg patrickb: right here! :)
patrickb: I saw your request, but unfortunately, I'm useless in that sense. 18:21
patrickb vrurg: I'm looking at the git-reference PR again. I have little idea about the ins and outs of BEGIN blocks and thus little idea to help me find a nicer way for the BEGIN block debacle... 18:22
vrurg: That's OK. I just want to make sure people think about it in time and decide whether or not they want to get involved. Two days before the deadline is simply to late for a thought through decision or brainstorming for ideas. That's why I'm actively poking people. 18:23
vrurg patrickb: Let me put it this way about BEGINs: when Foswiki project started long ago as TWiki, people thought: a few lines in a BEGIN block is fine. It all ended up with monstrous, unmanageable, and fragile code which relied on peculiarities of compile-time execution. 18:26
patrickb: It would even be better if you just run an external script from BEGIN which would do the same task.
patrickb vrurg: Can you point me into a direction of how to change it? As far as I understand it, the submodule imports need to be done before using the nqp-configure repo, thus the BEGIN block. I'm willing to do that, it's just that the word "even" in that sentence sounds like one should actually come up with a better alternative. :-) 18:28
vrurg In this context 'even' means 'better than big BEGIN' :) 18:29
vrurg is thinking about it yet....
patrickb: the quick solution is to get the submodule update code, make a script out of it and execute the script within BEGIN. Because the alternative would be extracting all code from Configure.pl into a module and, perhaps, make it a class. Then we'd get more freedom. 18:32
But the second solution is too time-costly.
patrickb vrurg: OK, then I'll go for the script. Thanks for the heads up! 18:33
vrurg patrickb: good luck!
patrickb: BTW, I think we must start thinking of what to do about perl6- prefixed executables. Time to rename them as well, but have to consider consequences. 18:34
patrickb vrurg: You mean about the ones in the build dir? 18:34
vrurg Yes, them. We also install them.
And not only moar backend, but jvm and js too which scares me a lot. 18:36
patrickb I'd say there is little potential for any breakage when renaming those. For the ones that are installed I'm a little less confident, as it's difficult to know how users treat the installed files. But my gut feeling says "What could go wrong?"
patrickb I've never done much dabbling in jvm / js. Can't say much about those. :-/ 18:37
vrurg patrickb: We'd have to have symlinks for quite some time. But, anyway, I'd like to spare this week for another project and a new post about roles. Hope to get back to this next week. Perhaps, will open an issue to welcome as much discussion as possible. 18:40
patrickb vrurg++ 18:41
tony-o AlexDaniel: http::server::async was written before the threading copied context in moar, even :-) 18:51
i reckon i started that in 2011
err, probably 2012 18:52
AlexDaniel sure, but Bisectable was written in 2015 or 2016 18:53
tony-o lizmat: AlexDaniel: is there a new way to getting stuff in the weekly?
AlexDaniel tony-o: new way? weekly: should work 18:54
weekly: new exciting stuff! (just a test)
notable6 AlexDaniel, Noted! (weekly)
tony-o weekly: deathbyperl6.com/zef-ecosystem/
notable6 tony-o, Noted! (weekly)
tony-o ah, ty, dunno why i can't remember that
i was referring to your conversation about migrating to cro
i would recommend it 18:55
AlexDaniel right :)
patrickb vrurg: Mind to have another look at the PRs? 20:10
vrurg patrickb: perhaps later today or tomorrow. 20:11
patrickb .seen rba 20:47
tellable6 patrickb, gist.github.com/b1d9249455b34adb11...19c61400ac
patrickb .tell rba If you find the time to have a look at github.com/perl6/rakudo.org/pull/32 that'd be great. I'm more and more blocked by that merge... 20:56
tellable6 patrickb, I'll pass your message to rba
patrickb I'm off to bed. Night everyone! o/
rba patrickb: will take care of your pr tomorrow. 21:21
tellable6 rba, I'll pass your message to patrickb
Geth rakudo/release-2020.01: 6 commits pushed by Altai-man++, (Elizabeth Mattijsen)++
rakudo: Altai-man++ created pull request #3438:
Release 2020.01
21:23
samcv .tell patrickb and nine: well it depends on the mentee I think. But best to set expectations early. But I was not super active, but gave more domain specific knowledge as well as advice on algorithms and way to aproach problems for the student 21:34
tellable6 samcv, I'll pass your message to patrickb
samcv I got a message from jj about mentoring for outreachy. i would be interested, well i'm not sure what to do it on. but i could come up with something if needed. not sure how specific i should be for listing my mentorship, like as far as the tasks 21:35
i'm not sure how much it differs from GSoC. GSoC you need to set out the plan early on 21:36
Geth nqp/compressed_lex_loc_types_serialization: c383acd8ed | (Timo Paulssen)++ | src/QAST/Block.nqp
use base 36 for cuids instead of base10

longest cuid in the core setting is now 3 digits instead of 5 as before. The savings are tiny in total, though.
22:50