IRCloggy #perl6-dev 2019-08-16

Logs Search ←Prev date Next date→ Channels Documentation

Provider of IRC logs since 2005.
WARNING: As Freenode became unjoinable and lost all warnings in topics, we cannot log channels on Freenode anymore.

2019-08-16

← reportable6 left00:00
vrurg There're few locations in World where nqp::getcomp is used. Why isn't it pre-cached in an attribute?00:00
Wouldn't it be slightly faster?00:00
→ reportable6 joined00:00
timotimo i could imagine that getcomp is fast00:09
it's a hash lookup, i see00:09
though i suppose with the typical number of compilers registered at the same time being probably between 2 and 5 a little list could be faster00:10
← lucasb left00:34
vrurg timotimo: World only deals with "perl6". So, I gues this one could be pre-cached in an attribute.00:57
Just hope that attribute access is optimizied.00:58
timotimo do you have a benchmark or measurement or something?01:04
i've got some outputs01:05
hm. while running, every time INITIALIZE-DYNAMIC is called, eh?01:07
ah, that is to get at language version01:08
my code uses array access and runs into the "out of range" condition quite often01:09
which wants to see if $*INDEX is there to put in the exception01:09
vrurg timotimo: I didn't do any testing so far. Just completing new subtest semantics for 6.e and stumbled upon this.01:10
It was just thinking aloud.01:10
timotimo right01:11
vrurg BTW, I postponed my games with gdb. I realized that it was hanging before even reaching any mutex on the thread context. Moreover, the freezing point is deeply inside utf8 processing, where it walks over graphemes.01:12
I tried to debug it and it was even more confusing because as long as I tried to step opver the macro – it was freezing. But step into – and it worked!01:12
So long, as I don't currently have direct need in debuging moar, I decided to postpone it for better times. :)01:13
timotimo in some places getcomp is used to check if the backend is moar or jvm or whatever01:14
in files that use gen-comp, we could replace that with #?if pieces01:14
get-cat*01:14
gen-cat*01:14
vrurg BTW, I never seen #? been documented. Is it somewhere?01:15
timotimo hm, dunno01:16
it's entirely a thing gen-cat.pl does, though, so not sure where that doc would go01:16
vrurg Oh, ok, sure.01:18
I didn't know gen-cat does it. Now the meaning of what you said above makes better sense.01:19
timotimo oops, the gist makes my browser kind of freeze up01:21
vrurg And I found the backend piece. Makes total sense replacing it with #?if01:21
timotimo well, many places that do it01:22
i don't think it's exceptionally slow, but it could be 100% faster01:22
vrurg A little bit here, a little bit there...01:23
timotimo https://gist.githubusercontent.com/timo/1546434174a4556a64e5a26b31e185a4/raw/7132d3932bfcb51b7dfed33df0bb992fee97a9ce/gistfile1.txt - this is a very very large text file01:23
it has a stack trace whenever nqp::getcomp is called01:23
during the compilation and running of a little script, rc-forest-fire01:23
hm, actually01:24
about 1/3rd in the compiler ends01:24
the rest is almost all just DYNAMIC -> INITIALIZE-DYNAMIC01:24
vrurg Method calls on getcomp are definitely not the fastest thing even if getcomp itself is fast enough.01:32
So, in some cases it worth caching not the compiler itself, but method output if it's persistent per-unit.01:32
← pamplemousse left03:02
Geth ¦ rakudo/master: 21 commits pushed by (Vadim Belman)++03:10
¦ rakudo/master: review: https://github.com/rakudo/rakudo/compare/7e1062659fb6...ef9d1354979a03:10
¦ roast/master: 5 commits pushed by (Vadim Belman)++03:11
¦ roast/master: b49238995b | Modified tests to conform new subset logic. 03:11
¦ roast/master: 26ff0d6766 | Merge branch 'master' of https://github.com/perl6/roast into problem-solving-3 03:11
¦ roast/master: f2be3b23af | Revert "Modified tests to conform new subset logic." 03:11
¦ roast/master: c15db774c3 | Change tests for the new subset semantics. 03:11
¦ roast/master: 9bd7dcdec2 | Merge pull request #547 from vrurg/problem-solving-3 03:11
¦ roast/master: review: https://github.com/perl6/roast/compare/381974e9fa94...9bd7dcdec2b003:11
vrurg Almost half a year marathon is finally over. Perhaps...03:13
→ travis-ci joined03:54
travis-ci Rakudo build passed. Vadim Belman 'Merge pull request #2946 from vrurg/problem-solving-303:54
https://travis-ci.org/rakudo/rakudo/builds/572575092 https://github.com/rakudo/rakudo/compare/7e1062659fb6...ef9d1354979a03:54
← travis-ci left03:54
← Kaiepi left04:12
→ Kaiepi joined04:12
← reportable6 left06:00
→ reportable6 joined06:03
ChanServ set mode: +v06:03
Geth ¦ nqp: cygx++ created pull request #573: Enable DLL-releated MoarVM ops 06:52
¦ nqp: review: https://github.com/perl6/nqp/pull/57306:52
¦ rakudo: cygx++ created pull request #3123: implement Nativecall::DLL 06:54
¦ rakudo: review: https://github.com/rakudo/rakudo/pull/312306:54
→ lizmat joined06:55
← lizmat left06:56
→ lizmat joined08:57
Geth ¦ problem-solving/path-to-raku: 31a00384a6 | (Elizabeth Mattijsen)++ | solutions/language/PATH-TO-RAKU.md09:04
¦ problem-solving/path-to-raku: Refince external references section 09:04
¦ problem-solving/path-to-raku:09:04
¦ problem-solving/path-to-raku: Add specific mention of Rosetta Code09:04
¦ problem-solving/path-to-raku: review: https://github.com/perl6/problem-solving/commit/31a00384a609:04
lizmat s/refince/refine/ duh :-(09:05
← Kaiepi left09:30
→ Kaiepi joined09:34
Geth ¦ problem-solving/path-to-raku: 92fd411b67 | (Elizabeth Mattijsen)++ | solutions/language/PATH-TO-RAKU.md09:37
¦ problem-solving/path-to-raku: Open the door to a joint rename / next version event 09:37
¦ problem-solving/path-to-raku:09:37
¦ problem-solving/path-to-raku: Also fix some erroneous backslashes09:37
¦ problem-solving/path-to-raku: review: https://github.com/perl6/problem-solving/commit/92fd411b6709:37
¦ problem-solving/path-to-raku: cfd072d974 | (Elizabeth Mattijsen)++ | solutions/language/PATH-TO-RAKU.md09:47
¦ problem-solving/path-to-raku: Mention a "Raku Foundation" as part of YAS 09:47
¦ problem-solving/path-to-raku: review: https://github.com/perl6/problem-solving/commit/cfd072d97409:47
→ patrickb joined10:04
patrickb o/10:04
← lizmat left10:16
kawaii \o10:53
|Tux| Rakudo version 2019.07.1-160-gef9d13549 - MoarVM version 2019.07.1-74-g5b174f52811:05
csv-test-xs-20 0.437 - 0.44011:05
csv-ip5xs 0.679 - 0.73811:05
test-t --race 0.785 - 0.80711:05
test-t 1.662 - 1.69211:05
csv-ip5xs-20 4.966 - 4.97011:06
test 6.539 - 7.05611:06
test-t-20 --race 9.014 - 9.16511:06
csv-parser 21.629 - 22.30211:06
test-t-20 29.532 - 29.68911:06
patrickb .tell AlexDaniel I keep extending one of my "Perl 6 rename discussion" posts that contains a list of steps to do. It believe it can serve as a good starting point for the actual work given we do decide to rename.11:09
.tell AlexDaniel But I'm reluctant to put that in a more formal place, as that might be seen as taking the second step before the first one. (First one being actually deciding on the rename.)11:11
And with that I'm back to vacationing. o/11:13
← patrickb left11:13
→ patrickb joined11:14
patrickb .tell AlexDaniel Forgot the link, here it is: https://github.com/perl6/problem-solving/issues/81#issuecomment-52021603111:15
← patrickb left11:15
→ lizmat joined11:19
← reportable6 left12:00
→ reportable6 joined12:04
← lizmat left12:11
→ lizmat joined12:14
AlexDaniel hmm12:33
lizmat: ↑ see that list12:34
lizmat AlexDaniel: sorry, what list (was offline for a bit)12:43
AlexDaniel lizmat: https://colabti.org/irclogger/irclogger_log/perl6-dev?date=2019-08-16#l10212:44
lizmat: this comment: https://github.com/perl6/problem-solving/issues/81#issuecomment-52021603112:45
lizmat Ah, hadn't noticed it is being expanded... wlll look at that12:45
AlexDaniel lizmat: how about we close the thread for a week?12:46
lizmat: I'm tired waking up to a pagefull of notifications12:46
lizmat I'm fine, if you can... seems I can not :-) Just close it, but that wouldn't stop comments12:46
AlexDaniel there are still some useful bits being mentioned, but you have to look really close to see them12:47
reason “too heated” that sounds about right12:47
lizmat yeah, thanks12:50
AlexDaniel lizmat: do you see the comment box right now?12:51
jnthn Yes, but...some folks (like moritz++) who will vote on it are still chiming in, among those who are being unpleasant. But maybe those who are part of the perl 6 org can still post?12:51
lizmat I think moritz can still post now12:51
AlexDaniel lizmat: but can you?12:51
I think I made you the owner of perl6 org a few days ago12:52
lizmat seems I can12:52
jnthn Ah, it's limited to collaborators12:52
I guess that's folks in the Perl 6 org?12:52
If so, I'm fine with it.12:53
I think I've heard enough from the outside by now. :P12:53
(Also, I marked a couple of them that were general rants about Perl 6 as off-topic because, well, they are.)12:54
AlexDaniel thank you12:54
kawaii: hello12:55
kawaii AlexDaniel: hello to you too friend12:55
AlexDaniel kawaii: can you tell me if you can still see the comment box here? https://github.com/perl6/problem-solving/issues/8112:56
kawaii: like, can you still leave comments on that thread or not?12:56
kawaii AlexDaniel: doesn't look like I can!12:57
AlexDaniel kawaii: ok, I see. Thanks!12:59
anyway https://github.com/perl6/problem-solving/issues/81#issuecomment-52200031912:59
AlexDaniel takes a deep breath13:02
AlexDaniel jnthn: I think it's limited to this list: https://github.com/orgs/perl6/people?utf8=%E2%9C%93&query=+role%3Aowner13:03
btw toddr is in it because there were some potential limitations for repo management for the upcoming old-issue-tracker repo13:05
kawaii It was an excellent thread with some really good discussion points13:06
AlexDaniel: do you know about the status of the star release?13:06
AlexDaniel kawaii: no, you need to ask hankache and clarkema13:07
kawaii: or maybe open a new ticket here? https://github.com/rakudo/star/issues13:07
asking for a new release13:07
kawaii I'm sure one of them will be notified by you mentioning their names, no need for me to harass further :)13:07
AlexDaniel kawaii: not exactly13:09
kawaii: clarkema is on #perl6 but not here13:09
kawaii ah then I must be annoying it seems :(13:10
oh looks like you already poked him in #perl613:10
:)13:10
AlexDaniel maybe today is the day when I'll finally bring tellable6 up13:12
wish me luck x)13:12
vrurg AlexDaniel: good luck! :)13:12
greppable6: use v6\.\*13:15
greppable6 vrurg, 6 lines, 3 modules: https://gist.github.com/5d3859367f37a5561e7cba03ae59883a13:15
vrurg greppable6: use v6\.e13:16
greppable6 vrurg, Found nothing!13:16
← Kaiepi left13:31
→ Kaiepi joined13:31
lizmat AlexDaniel jnthn looks like you cannot add emojis to comments anymore13:33
AlexDaniel lizmat: yeah13:33
there's no fine-grained control over this13:33
→ lucasb joined13:52
[Coke] wonders how many gists Whateverable has at this point13:58
[Coke] Oh: 10,14713:58
[Coke] wasn't expecting that to be public for some reason. :)13:58
moritz jnthn, lizmat: yes, I can still comment (I'm org owner as well)14:03
AlexDaniel [Coke]: it's weird, there are several ways I'm abusing github yet the only complaint I got so far was that I have more than two accounts14:45
[Coke] regarding nuance comment on the ticket: I think we already lost the nuance battle, and this will not make it worse.14:47
AlexDaniel it's more like using than abusing, but I'm surprised I didn't trigger any automated ban hammer14:47
→ pamplemousse joined14:56
timotimo vrurg: did the list of "every place that calls getcomp" end up helping more than what we already discussed?15:12
Geth ¦ rakudo: 238f8e5739 | (Timo Paulssen)++ | src/core/CompUnit/PrecompilationRepository.pm615:48
¦ rakudo: Show stagestats for dependent precompilation 15:48
¦ rakudo:15:48
¦ rakudo: This way you can get much more info when your "stage parse"15:48
¦ rakudo: takes long, and you can more easily see the dependency15:48
¦ rakudo: structure of your projects (though of course modules that15:48
¦ rakudo: were already precompiled won't show up here)15:48
¦ rakudo: review: https://github.com/rakudo/rakudo/commit/238f8e573915:48
¦ rakudo: 960e5b4a43 | (Timo Paulssen)++ | src/core/CompUnit/PrecompilationRepository.pm615:48
¦ rakudo: flush stderr in stagestats report 15:48
timotimo ^- stagestats just became a whole lot funkier15:48
Geth ¦ rakudo: review: https://github.com/rakudo/rakudo/commit/960e5b4a4315:48
¦ rakudo: 0fbf92ca32 | (Timo Paulssen)++ | src/core/CompUnit/PrecompilationRepository.pm615:48
¦ rakudo: Merge branch 'nested_stagestats' 15:48
¦ rakudo: review: https://github.com/rakudo/rakudo/commit/0fbf92ca3215:48
timotimo i'd kind of like a RAKUDO_COMPILER_REPORT_PORT=9999 where it'd spit out like udp messages or something at different points in compilation, including when it precompiles dependent modules and such15:51
← pamplemousse left15:59
→ pamplemousse joined15:59
vrurg timotimo: I didn't get time for this. Finished with subsets at 11pm.16:15
timotimo no problem at all :)16:17
vrurg But I have noted it alongside some other stuff. And if things go this way, in few months my personal task list would be the size of issues list on rakudo... ;)16:18
timotimo i know that feeling16:19
vrurg m: subset SS of Int where { .defined }; my SS $v;16:19
camelia rakudo-moar ecf2b1e4f: ( no output )16:19
vrurg Which bot follows master, I don't remember?16:19
MasterDuke benchable6: HEAD compare sub foo($a, $b, $c, $d) { my $e = $a; my $f = $b; my $g = $c; my $h = $d; $e++; $f++; $g++; $h++; $e+$f+$g+$h }; my $s1 = 0; for ^1_000_000 -> $a, $b, $c, $d { $s1 = foo($a, $b, $c, $d) }; say $s1; ||| sub bar($a is copy, $b is copy, $c is copy, $d is copy) { $a++; $b++; $c++; $d++; $a+$b+$c+$d }; my $s2 = 0; for ^1_000_00016:19
benchable6 MasterDuke, starting to benchmark the 1 given commit16:19
MasterDuke -> $a, $b, $c, $d { $s2 = bar($a, $b, $c, $d) }; say $s2;16:19
benchable6 MasterDuke, No new data found16:19
vrurg m: use v6.e.PREVIEW; subset SS of Int where { .defined }; my SS $v;16:20
camelia rakudo-moar ecf2b1e4f: ( no output )16:20
MasterDuke benchable6: compare HEAD sub foo($a, $b, $c, $d) { my $e = $a; my $f = $b; my $g = $c; my $h = $d; $e++; $f++; $g++; $h++; $e+$f+$g+$h }; my $s1 = 0; for ^1_000_000 -> $a, $b, $c, $d { $s1 = foo($a, $b, $c, $d) }; say $s1; ||| sub bar($a is copy, $b is copy, $c is copy, $d is copy) { $a++; $b++; $c++; $d++; $a+$b+$c+$d }; my $s2 = 0; for ^1_000_00016:21
benchable6 MasterDuke, starting to benchmark the 1 given commit16:21
MasterDuke -> $a, $b, $c, $d { $s2 = bar($a, $b, $c, $d) }; say $s2;16:21
benchable6 MasterDuke, https://gist.github.com/10b2bab00c6eeb58f34555ef43f91e4916:21
timotimo oh no, the message was too long16:22
MasterDuke benchable6: compare HEAD sub foo($a,$b,$c,$d){my $e=$a;my $f=$b;my $g=$c;my $h=$d;$e++;$f++;$g++;$h++;$e+$f+$g+$h};my $s1=0; for ^1_000_000 -> $a,$b,$c,$d {$s1=foo($a,$b,$c,$d)}; say $s1; ||| sub bar($a is copy,$b is copy,$c is copy,$d is copy) {$a++;$b++;$c++;$d++;$a+$b+$c+$d};my $s2=0; for ^1_000_000 -> $a,$b,$c,$d {$s2=bar($a,$b,$c,$d)};say $s2;16:23
benchable6 MasterDuke, starting to benchmark the 1 given commit16:23
MasterDuke, ¦HEAD: «Benchmark: ␤«timed out after 10 seconds»»16:24
AlexDaniel vrurg: “Which bot follows master, I don't remember?” any bot that's not broken xD16:24
MasterDuke benchable6: compare HEAD sub foo($a,$b,$c,$d){my $e=$a;my $f=$b;my $g=$c;my $h=$d;$e++;$f++;$g++;$h++;$e+$f+$g+$h};my $s1=0; for ^500_000 -> $a,$b,$c,$d {$s1=foo($a,$b,$c,$d)}; say $s1; ||| sub bar($a is copy,$b is copy,$c is copy,$d is copy) {$a++;$b++;$c++;$d++;$a+$b+$c+$d};my $s2=0; for ^500_000 -> $a,$b,$c,$d {$s2=bar($a,$b,$c,$d)};say $s2;16:24
benchable6 MasterDuke, starting to benchmark the 1 given commit16:24
MasterDuke, ¦HEAD: «Benchmark: ␤«timed out after 10 seconds»»16:24
AlexDaniel moritz: I think camelia is still not fixed16:24
MasterDuke: maybe try committable first?16:25
MasterDuke AlexDaniel: can you increase benchable6's timeout?16:25
AlexDaniel aaah sorry it's `compare` thing16:25
benchable6: vars16:25
benchable6 AlexDaniel, timeout=1016:25
AlexDaniel benchable6: timeout=3016:25
benchable6 AlexDaniel, timeout is now set to “30” (default value is “10”)16:25
AlexDaniel try again?16:25
MasterDuke ah ha, forgot about that!16:25
benchable6: compare HEAD sub foo($a,$b,$c,$d){my $e=$a;my $f=$b;my $g=$c;my $h=$d;$e++;$f++;$g++;$h++;$e+$f+$g+$h};my $s1=0; for ^500_000 -> $a,$b,$c,$d {$s1=foo($a,$b,$c,$d)}; say $s1; ||| sub bar($a is copy,$b is copy,$c is copy,$d is copy) {$a++;$b++;$c++;$d++;$a+$b+$c+$d};my $s2=0; for ^500_000 -> $a,$b,$c,$d {$s2=bar($a,$b,$c,$d)};say $s2;16:25
benchable6 MasterDuke, starting to benchmark the 1 given commit16:25
AlexDaniel I'm not sure if that thing works, actually16:25
but let's see16:25
benchable6 MasterDuke, https://gist.github.com/0e4acc92e80490b6ee2b5827093f08b416:25
AlexDaniel wow it does work xD16:26
← lizmat left16:26
MasterDuke occasionally i write some code that works some of the time16:26
timotimo so "is copy" is a lot faster?16:26
MasterDuke other way around16:26
timotimo oh?16:27
damn.16:27
→ lizmat joined16:27
← lizmat left16:27
AlexDaniel timotimo: yeah, I've seen that somewhere in real code16:28
MasterDuke benchable6: timeout=12016:28
benchable6 MasterDuke, timeout is now set to “120” (default value is “10”)16:28
MasterDuke benchable6: compare HEAD sub foo($a,$b,$c,$d){my $e=$a;my $f=$b;my $g=$c;my $h=$d;$e++;$f++;$g++;$h++;$e+$f+$g+$h};my $s1=0; for ^1_000_000 -> $a,$b,$c,$d {$s1=foo($a,$b,$c,$d)}; say $s1; ||| sub bar($a is copy,$b is copy,$c is copy,$d is copy) {$a++;$b++;$c++;$d++;$a+$b+$c+$d};my $s2=0; for ^1_000_000 -> $a,$b,$c,$d {$s2=bar($a,$b,$c,$d)};say $s2;16:28
benchable6 MasterDuke, starting to benchmark the 1 given commit16:28
MasterDuke, https://gist.github.com/85051c7cf2fe0fab83918ba26b5c94f616:29
MasterDuke hm, i didn't see quite that big a difference locally16:29
→ Ven`` joined16:32
MasterDuke jnthn: fyi, ^^^16:32
jnthn MasterDuke: Is the `is copy` itself slower, or is it to do with an effect it has on how the ++ and + can be optimized?16:35
MasterDuke jnthn: dunno. that was just the first thing i thought of that would exercise the need for `is copy` (or the equivalent)16:36
same different if i assign `rand` to the variables instead of increment them16:40
*difference in time taken16:40
← Kaiepi left16:45
→ Kaiepi joined16:45
MasterDuke c16:49
moritz m: say $*PERL.version16:55
camelia rakudo-moar ecf2b1e4f: OUTPUT: «v6.d␤»16:55
moritz m: say $*COMPILER.version16:55
camelia rakudo-moar ecf2b1e4f: OUTPUT: «Dynamic variable $*COMPILER not found␤ in block <unit> at <tmp> line 1␤␤»16:55
moritz the version number at start looks stuck, yes. Will need to look at this in more detail16:57
← Ven`` left17:07
→ Ven`` joined17:09
← Ven`` left17:13
vrurg m: say $*PERL.compiler.version17:14
camelia rakudo-moar ecf2b1e4f: OUTPUT: «v2019.07.69.gecf.2.b.1.e.4.f␤»17:14
← lucasb left17:17
vrurg jnthn: do you mind of introducing CORE::<lang-rev>:: pseudo-packages?17:34
R#311217:34
synopsebot R#3112 [open] : https://github.com/rakudo/rakudo/pull/3112 [6.e] Implement CORE::<lang-rev> pseudo-packages 17:34
← samcv left17:43
→ samcv joined17:48
← reportable6 left18:00
→ reportable6 joined18:02
ChanServ set mode: +v18:02
→ lucasb joined18:21
Geth ¦ rakudo/master: 8 commits pushed by (Vadim Belman)++18:47
¦ rakudo/master: da65fb5bae | Fix for rakudo/rakudo#2178 18:47
¦ rakudo/master: 6e24ad57f3 | Merge branch 'master' of https://github.com/rakudo/rakudo into issue_2178 18:47
¦ rakudo/master: 2e915d74ee | Fixed a bug when a wrapped method is called first 18:47
¦ rakudo/master: f5e40b2f7b | Removed extra spaces before signatures 18:47
¦ rakudo/master: 7d8cba1cf3 | Merge branch 'master' of https://github.com/rakudo/rakudo into issue_2178 18:47
¦ rakudo/master: d6985fd67d | Merge branch 'master' of https://github.com/rakudo/rakudo into issue_2178 18:47
synopsebot RAKUDO#2178 [open] : https://github.com/rakudo/rakudo/issues/2178 .wrap of a method breaks callsame/nextsame/etc. 18:47
Geth ¦ rakudo/master: 1463ce02ff | Merge branch 'master' of https://github.com/rakudo/rakudo into issue_2178 18:47
¦ rakudo/master: 2a5b642de3 | Merge pull request #2749 from vrurg/issue_2178 18:47
¦ rakudo/master: review: https://github.com/rakudo/rakudo/compare/0fbf92ca3227...2a5b642de3eb18:47
¦ roast/master: 5 commits pushed by (Vadim Belman)++18:47
¦ roast/master: 632cde2831 | Tests for dispatching with wrapped methods 18:47
¦ roast/master: f97749dd8c | Merge branch 'master' of https://github.com/perl6/roast into issue_2178 18:47
¦ roast/master: 6e200b9b16 | Merge branch 'master' of https://github.com/perl6/roast into issue_2178 18:47
¦ roast/master: c248592dc5 | Merge branch 'master' of https://github.com/perl6/roast into issue_2178 18:47
¦ roast/master: 012b723210 | Merge pull request #518 from vrurg/issue_2178 18:47
¦ roast/master: review: https://github.com/perl6/roast/compare/9bd7dcdec2b0...012b7232109d18:47
→ grayrider joined19:10
← grayrider left19:33
→ Ven`` joined19:42
← pamplemousse left19:56
→ pamplemousse joined20:07
← pamplemousse left20:26
→ pamplemousse joined20:32
← epony left21:25
← Ven`` left21:51
vrurg AlexDaniel: since you're available yet, I'm not really happy about `CORE::v6d` naming as it's rather long. Besides, it is not decided yet if we keep or drop 6. version prefix, even though I'd be strongly opposed to changing versioning model.22:20
AlexDaniel vrurg: it is not yet decided if we're going to drop it or not, yet you're dropping it :)22:25
and what do you mean “long”22:26
two characters?22:26
honestly, that doesn't sound very convincing to me :)22:26
vrurg AlexDaniel: No, I'm not. Terminlogy-wise we have version (6.e, v6.e) and we have revision (e).22:26
jnthn I don't think it'll be used often enough to justify making it especially short22:27
vrurg I'm not dropping.22:27
AlexDaniel if not dropping, then it should also work with 7.d even if we never bump the version to 722:28
vrurg Another point for just letter is readability. CORE::v6c::Class, CORE::v6d::Class vs CORE::c::Class, CORE::d::Class22:28
AlexDaniel v6d is more readable in this case to me22:28
stands out a bit more22:28
jnthn agrees with AlexDaniel22:28
jnthn Though I still wonder about the adverb approach (CORE:ver<6.d>)22:29
vrurg My braing is still in all-uppercase variant of CORE::V6D which looked really ugly.22:29
jnthn: CORE:ver<6.d>::PseudoStash – pretty much line noise looking.22:30
jnthn I parse "line noise" as "I don't need to consider this argument" :P22:30
vrurg is just trying to formulate it properly.22:31
jnthn But seriously, if adverbs - with feature all over Perl 6 - are line noise, well... :)22:31
*which22:31
The argument for it is regularity, I guess.22:31
vrurg I like PseudoStash:ver<6.d> for direct reference. But for introspection CORE::v6d:: is better.22:31
AlexDaniel jnthn: actually, I kinda agree that it is a bit too symbol-y22:31
jnthn use Foo:ver<1.2>22:31
AlexDaniel but I wouldn't say it's too bad…22:32
jnthn m: use v6.d22:32
vrurg TIMTOWTDI22:32
camelia rakudo-moar ecf2b1e4f: ( no output )22:32
jnthn m: use v6d22:32
camelia rakudo-moar ecf2b1e4f: ( no output )22:32
jnthn Huh, I'd forgotten you can write the second :)22:32
AlexDaniel O_o22:32
vrurg We can have both and use depending on personal taste and task.22:33
AlexDaniel you… can…?22:33
jnthn Maybe I hadn't forgot :P22:33
AlexDaniel m: say v6d22:33
camelia rakudo-moar ecf2b1e4f: OUTPUT: «v6.d␤»22:33
vrurg m: say Version.new('v6d')22:33
camelia rakudo-moar ecf2b1e4f: OUTPUT: «vv.6.d␤»22:33
jnthn Anyway, there goes my argument that it's different from what you write in the `use` statement :P22:33
AlexDaniel ok then I don't see anything wrong with ::v6d::22:33
vrurg besides that it does it this way.22:33
AlexDaniel I thought it wasn't really a valid version, but turns out it is22:33
vrurg Ok, I rename it. The only thing made me using ::D is to follow all-uppercase standard.22:34
But since it's second level, it can be treated differently.22:35
Thanks! I get it fixed and merge. This will unblock R#310322:36
synopsebot R#3103 [open] : https://github.com/rakudo/rakudo/pull/3103 [6.e][tests needed] Return Failure from failed P6-level .parse on 6.e 22:36
jnthn I'm still just a tiny bit...discontented, I guess...that we're introducing a discontinuity where CORE::foo means a lookup in CORE, except when it's followed by a specific pattern.22:36
I agree that we're not going to have a symbol v6d or so on22:36
vrurg jnthn: consider it a lookup too. It's like symbols containting the specific cores. Why not?22:36
jnthn vrurg: Well, how is it actually implemented? :)22:37
If it's by each CORE.setting saying `my constant v6c := UNIT` or something I guess I can buy it...kind of :)22:37
timotimo CORE::v6d::v6c::v6e::... :)22:38
jnthn :P22:38
Anyway, I can go with CORE::v6d, I think22:39
MasterDuke but, eventually, how will distinguish between CORE::v60 and CORE::v6d in casual conversation!?!?!22:39
vrurg jnthn: Because it has to work compile time, it's supported by World::find_symbol_in_setting22:39
And run-time is provided by PseudoStash.22:39
jnthn Hm, OK22:39
vrurg timotimo: v6e will be a Failure22:40
jnthn Hm, compile time?22:40
What if I say CORE::v6d::.keys, for example?22:40
Or are you saying it resolves up to the v6d bit at compile time?22:41
MasterDuke btw, in case anybody wants something else to work on, `--profile-compile` of the rakudo build still dies22:41
vrurg jnthn: It will be handled by run-time. :)22:41
jnthn OK22:41
← MasterDuke left22:47
vrurg Now, I can't get rid of the idea of installing the actual symbols on COREs...22:49
Ah, nevermind, it won't work...22:50
← pamplemousse left23:02
→ pamplemousse joined23:07
← pamplemousse left23:11
AlexDaniel Dogbert4711 dogbert11 dogbert17 dogbert17_ dogbert2 dogbert21 dogbert2_23:40
:D23:40

Logs Search ←Prev date Next date→ Channels Documentation