🦋 Welcome to the IRC channel of the core developers of the Raku Programming Language (raku.org #rakulang). This channel is logged for the purpose of history keeping about its development | evalbot usage: 'm: say 3;' or /msg camelia m: ... | Logs can be inspected at colabti.org/irclogger/irclogger_log/raku-dev | For MoarVM see #moarvm
Set by lizmat on 26 April 2021.
00:02 reportable6 left 00:03 reportable6 joined 00:10 finsternis joined 00:19 dogbert17 joined 00:23 dogbert11 left 00:24 dogbert11 joined 00:26 dogbert17 left 01:10 frost-lab joined 01:36 kvw_5_ joined 01:39 kvw_5 left 02:39 greppable6 left, linkable6 left, benchable6 left, bloatable6 left, nativecallable6 left, evalable6 left, reportable6 left, tellable6 left, unicodable6 left, statisfiable6 left, coverable6 left, notable6 left, shareable6 left, sourceable6 left, quotable6 left, bisectable6 left, squashable6 left, committable6 left, releasable6 left 02:40 bisectable6 joined, statisfiable6 joined, quotable6 joined, reportable6 joined, nativecallable6 joined, releasable6 joined 02:41 unicodable6 joined, benchable6 joined, shareable6 joined, linkable6 joined, tellable6 joined, notable6 joined 02:42 greppable6 joined, evalable6 joined, sourceable6 joined, bloatable6 joined, committable6 joined, coverable6 joined, squashable6 joined 04:54 Kaiepi left 04:55 Kaiepi joined 05:08 Kaiepi left 05:52 Kaiepi joined 06:02 reportable6 left, reportable6 joined 06:56 domidumont joined
tyil Geth: uptime 07:48
Geth 2 days, 22 hours, 11 minutes, and 4 seconds
tyil wonder if that's a new record :p
lizmat :-) 09:16
m: my %h; %h<a> := { foo => 1, bar => 2 }; %h<b> := { foo => 3 }; dd %h<a b c> # fully expected 09:17
camelia ({:bar(2), :foo(1)}, {:foo(3)}, Any)
lizmat m: my %h; %h<a> := { foo => 1, bar => 2 }; %h<b> := { foo => 3 }; dd %h<a b c>:n # WTF? Pairs ?
camelia Unexpected named argument 'n' passed
in block <unit> at <tmp> line 1
lizmat m: my %h; %h<a> := { foo => 1, bar => 2 }; %h<b> := { foo => 3 }; dd %h<a b c>:v # WTF? Pairs ?
camelia (:bar(2), :foo(1), :foo(3))
lizmat m: my %h; %h<a> = { foo => 1, bar => 2 }; %h<b> = { foo => 3 }; dd %h<a b c>:v # WTF? Pairs ?
camelia (${:bar(2), :foo(1)}, ${:foo(3)})
lizmat I wonder whether that is intentional or not 09:18
bisectable6: my %h; %h<a> := { foo => 1, bar => 2 }; %h<b> := { foo => 3 }; dd %h<a b c>:v
bisectable6 lizmat, Will bisect the whole range automagically because no endpoints were provided, hang tight
lizmat, Output on all releases: gist.github.com/5e6e6c5e9bfd3bb363...a6008a2966 09:19
lizmat, More than 4 changes to bisect, please try a narrower range like old=2021.04 new=HEAD
lizmat bisectable6: old=2020.01 my %h; %h<a> := { foo => 1, bar => 2 }; %h<b> := { foo => 3 }; dd %h<a b c>:v 09:20
bisectable6 lizmat, On both starting points (old=2020.01 new=816281b) the exit code is 0 and the output is identical as well
lizmat, Output on both points: «(:foo(1), :bar(2), :foo(3))␤»
lizmat guess it is a side-effect of not being containerized
09:27 squashable6 left 09:29 squashable6 joined 09:33 squashable6 left 09:38 squashable6 joined 09:40 squashable6 left 09:41 squashable6 joined 09:46 dogbert11 left
lizmat gist.github.com/lizmat/c165bb0cbf9...767486093d # map inside a map doesn't map ? 10:24
I'd expect that to die
because of the inner map
Geth rakudo/rakuast: da4dc8a129 | (Jonathan Worthington)++ | 5 files
Basic RakuAST node for token/regex/rule decls
lizmat I'm I going crazy, or is that supposed to work ?
moritz is this lazy evaluation causing surprises? 10:56
lizmat yeah, it is 10:58
mix in some "do for" s to fix 10:59
or some .eager somewhere
now that I recognize the issue, I can fix it in my code :-)
hmmm... I wonder if .sort could use a :reverse arg 11:01
it would just be wrapping the resulting Seq with another iterator
11:16 lichtkind joined 11:21 squashable6 left 11:25 squashable6 joined 12:02 reportable6 left, reportable6 joined
[Tux] Rakudo v2021.04-28-g816281b91 (v6.d) on MoarVM 2021.04-47-g7be286190
csv-ip5xs0.915 - 1.058
csv-ip5xs-209.510 - 10.050
csv-parser28.356 - 29.741
csv-test-xs-200.376 - 0.376
test7.873 - 8.076
test-t2.128 - 2.215
test-t --race0.922 - 1.023
test-t-2035.982 - 37.494
test-t-20 --race11.155 - 11.279
13:22 frost-lab left
[Coke] "No, Mr. Bond, I'd expect that to die." 14:28
15:17 domidumont left
[Coke] anyone in particular maintaining github.com/raku/nqp-configure ? 15:41
If I want to change a branch of nqp (e.g.) to use a different nqp-configure, what do I need to do other than edit .gitmodules ? (doing a git submodule update does nothing, removing 3rd-party/nqp-configure and doing submodule init/update gives me back the original one...) 15:52
found it (sync) 16:01
Geth rakudo/rakuast: 05f7740c15 | (Jonathan Worthington)++ | 10 files
Flesh out RakuAST error reporting

  * Collect typed and untyped worries and sorries from the compiler
  * Form those into the X::Comp::Group when there are multiple things to
  * Provide a means for RakuAST nodes to perform an action at check time
   and report sorries and worries; implement two cases of this to show
   that it works
  * Report any potential difficulties and check-time errors at the end of
  * Also throw any check-time sorries detected when we do an AST EVAL
[Coke] I normally treat submodules as readonly - if i want to be working on the submodule, can I just cd to it and treat it like a normal git clone? Any special precautions to take? 16:11
also, I feel the need to add $*lorries somewhere to compliment sorries & worries. :P 16:15
(also, TIL: porry, gorry) 16:22
16:58 Kaiepi left, Kaeipi joined 17:03 domidumont joined 17:15 Merfont joined, Kaeipi left 17:54 domidumont left 18:02 reportable6 left 18:03 reportable6 joined 18:12 Merfont left 18:13 Merfont joined
nine [Coke]: yes, you can 19:17
21:16 MasterDuke joined
lizmat m: dd "foo\nbar\n\n".split("\n").join("\n") # completely expected 21:54
camelia "foo\nbar\n\n"
lizmat m: dd "foo\nbar\n\n".split("\n").squish.join("\n") # que ? 21:55
camelia "foo\nbar\n"
lizmat m: dd "foo\nbar\n\n".split("\n") # aaaah
camelia ("foo", "bar", "", "").Seq
23:26 quotable6 left, sourceable6 left, reportable6 left, statisfiable6 left, greppable6 left, unicodable6 left, nativecallable6 left, tellable6 left, bisectable6 left, coverable6 left, squashable6 left, linkable6 left, releasable6 left, notable6 left, evalable6 left, benchable6 left, shareable6 left, bloatable6 left, committable6 left, quotable6 joined, statisfiable6 joined, nativecallable6 joined, linkable6 joined 23:27 squashable6 joined, unicodable6 joined, committable6 joined, sourceable6 joined, bisectable6 joined, releasable6 joined, notable6 joined, tellable6 joined 23:28 coverable6 joined, greppable6 joined, reportable6 joined, evalable6 joined 23:29 bloatable6 joined, benchable6 joined, shareable6 joined