00:58 greppable6 left, quotable6 left, benchable6 left, nativecallable6 left, sourceable6 left, bisectable6 left, bloatable6 left, unicodable6 left, linkable6 left, committable6 left, shareable6 left, notable6 left, evalable6 left, tellable6 left, squashable6 left, releasable6 left, coverable6 left, statisfiable6 left 00:59 nativecallable6 joined, unicodable6 joined, quotable6 joined, committable6 joined 01:00 evalable6 joined, bisectable6 joined, tellable6 joined, shareable6 joined, statisfiable6 joined, benchable6 joined, sourceable6 joined, bloatable6 joined 01:01 releasable6 joined, linkable6 joined, greppable6 joined, coverable6 joined 01:02 squashable6 joined, notable6 joined 01:28 leont left 02:43 Kaiepi left, Kaiepi joined
releasable6 Next release in ≈6 days and ≈15 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 03:00
04:33 lucasb left 05:37 MasterDuke left 07:07 sena_kun joined 07:17 finsternis left 07:18 finsternis joined
Geth_ ¦ problem-solving: JJ assigned to rba Issue Manage GitHub organization secrets github.com/Raku/problem-solving/issues/240 08:17
lizmat Files=1336, Tests=113707, 220 wallclock secs (29.45 usr 8.52 sys + 3073.97 cusr 295.41 csys = 3407.35 CPU) 09:05
Geth_ rakudo: lizmat assigned to patrickbkr Issue ===SORRY!=== nqp-m outdated +build crash github.com/rakudo/rakudo/issues/3964
1971ba4642 | (Elizabeth Mattijsen)++ | src/core.e/hash_multislice.pm6

Just post-process the result in case of :!exists, as it will most likely be the less common thing to see.		 09:08
09:20 Altai-man joined 09:23 sena_kun left
lizmat m: sub foo(\a) { a(42) }; foo { .say } # that's LTA 10:01
camelia 5===SORRY!5=== Error while compiling <tmp>
Variable '&a' is not declared
at <tmp>:1
------> 3sub foo(\a) { 7⏏5a(42) }; foo { .say } # that's LTA
lizmat seems to happen in the optimizer
timotimo m: sub foo(\a) { a.(42) }; foo { .say } 10:18
camelia 42
timotimo consequence of a() being syntax for &a.() i guess? 10:19
you're saying it should give a "did you mean a.()" as a suggestion? 10:20
lizmat I'm not sure why it is considered to be an error ?
lizmat will use the .() workaround :-) 10:22
10:23 evalable6 left, linkable6 left
timotimo hm 10:25
m: sub foo(\A) { a(42) }; foo { .say }
camelia 5===SORRY!5=== Error while compiling <tmp>
Undeclared routine:
a used at line 1
10:25 evalable6 joined
timotimo m: sub foo(\A) { A(42) }; foo { .say } 10:25
camelia 5===SORRY!5=== Error while compiling <tmp>
Variable '&A' is not declared
at <tmp>:1
------> 3sub foo(\A) { 7⏏5A(42) }; foo { .say }
10:26 linkable6 joined
lizmat you don't even need a signature for it: 10:26
m: my \a = sub foo(|c) { dd |c }; a()
camelia 5===SORRY!5=== Error while compiling <tmp>
Variable '&a' is not declared
at <tmp>:1
------> 3my \a = sub foo(|c) { dd |c }; 7⏏5a()
timotimo right
lizmat timotimo: don't worry about it, I was just a bit WAT
timotimo this is purely a question of syntax
lizmat I understand why it is doing this now
timotimo yes but it's definitely give us a suggestion2 10:27
lizmat and since the optimizer will get a rewrite in rakuast anyway
timotimo should
lizmat I wouldn't spend any further time on it
timotimo okay
lizmat working on getting things like @a[1;*;3] to work, also with adverbs 10:28
timotimo yes that sounds like valuable work 10:31
lizmat m: multi a(\a,@b) { dd }; multi a(\a,@b,:$foo) { dd }; a 42, [] # so why does that dispatch to the one with the optional named ? 11:47
camelia sub a(\a, @b, :$foo)
lizmat m: multi a() is default { dd }; multi a(:$foo) { dd }; a' # golfed 11:49
camelia 5===SORRY!5=== Error while compiling <tmp>
Two terms in a row
at <tmp>:1
------> 3default { dd }; multi a(:$foo) { dd }; a7⏏5' # golfed
expecting any of:
infix
infix stopper
statement end
…
lizmat m: multi a() is default { dd }; multi a(:$foo) { dd }; a # golfed
camelia sub a(:$foo)
lizmat m: multi a() { dd }; multi a(:$foo) { dd }; a # golfed further
camelia sub a(:$foo)
timotimo because it can :D 11:50
12:05 leont joined 12:25 MasterDuke joined 12:31 leont left 12:37 MasterDuke left 13:21 sena_kun joined 13:23 Altai-man left 13:37 MasterDuke joined 13:45 ggoebel left
Geth_ roast: MasterDuke17++ created pull request #688:
Cover some Bool stuff		 14:17
14:17 ggoebel joined 14:31 [TuxCM] left
[Tux] Rakudo version 2020.09-65-g1971ba464 - MoarVM version 2020.09-12-g8c41f6692
csv-ip5xs0.825 - 0.847
csv-ip5xs-208.403 - 8.552
csv-parser25.238 - 27.566
csv-test-xs-200.387 - 0.392
test7.904 - 8.107
test-t1.890 - 2.172
test-t --race0.895 - 0.933
test-t-2032.039 - 32.463
test-t-20 --race9.412 - 10.038
 15:10
15:31 ggoebel left 15:56 ggoebel joined 15:58 ggoebel_ joined 16:01 ggoebel left
Geth_ rakudo/remove-restricted-setting: 26ec428ade | (Aleks-Daniel Jakimenko-Aleksejev)++ | 5 files
Remove RESTRICTED setting

RESTRICTED settings looks as if it is a security feature, but this issue cannot be approached with a blacklist. For example, the things that it blacklists are still available through method calls and nativecall, and there is just no way to plug all the possible holes. Moreover, those who actually need to run code securely will ... (10 more lines)		 16:11
rakudo: AlexDaniel++ created pull request #3965:
Remove RESTRICTED setting
roast: d4c131f6e2 | (Daniel Green)++ | S02-types/bool.t
Cover some Bool stuff
 16:12
roast: a64a289e09 | (Elizabeth Mattijsen)++ (committed using GitHub Web editor) | S02-types/bool.t
Merge pull request #688 from MasterDuke17/some_bool_coverage_tests

Cover some Bool stuff
16:18 Kaiepi left 16:20 ggoebel_ left, Kaiepi joined
Geth_ rakudo/remove-restricted-setting: 6ad69ab7d4 | (Aleks-Daniel Jakimenko-Aleksejev)++ | 5 files
Remove RESTRICTED setting

RESTRICTED settings looks as if it is a security feature, but this issue cannot be approached with a blacklist. For example, the things that it blacklists are still available through method calls and nativecall, and there is just no way to plug all the possible holes. Moreover, those who actually need to run code securely will ... (10 more lines)		 16:25
16:31 domidumont joined
sena_kun Ouch, I see some regressions. :( 16:43
Geth_ ¦ rakudo: Altai-man assigned to niner Issue Blin 2020.10, round 1 github.com/rakudo/rakudo/issues/3966 16:46
¦ rakudo: Altai-man assigned to lizmat Issue Blin 2020.10, round 1 github.com/rakudo/rakudo/issues/3966
nine I wonder if my uncommitted fix will help there 17:00
17:20 Altai-man joined 17:23 sena_kun left 17:37 domidumont left, lucasb joined 18:33 domidumont joined 18:34 domidumont left 19:01 Geth_ left 19:57 ggoebel_ joined 20:04 patrickb joined 20:19 patrickb left
lizmat pings tyil because Geth has gone AWOL 20:29
20:29 Geth joined
tyil lizmat: he's back :> 20:29
lizmat whee!
tyil++ 20:30
lizmat just merged github.com/Raku/roast/pull/689
20:40 Altai-man left 21:26 vrurg left 21:48 vrurg joined 21:49 vrurg left, vrurg joined, vrurg left
releasable6 Next release in ≈5 days and ≈19 hours. 1 blocker. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 23:00

Powered by Cro and the Raku® Programming Language.

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

Thank you!