🦋 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 available at irclogs.raku.org/raku-dev/live.html | For MoarVM see #moarvm
Set by lizmat on 8 June 2022.
ab5tract Heisenfactor 5 01:13
07:51 sena_kun joined
lizmat Xliff_: a git clone tells me: 09:27
tellable6 lizmat, I'll pass your message to Xliff_
lizmat warning: the following paths have collided (e.g. case-sensitive paths
on a case-insensitive filesystem) and only one from the same
colliding group is in the working tree:
'lib/GLib/URI.pm6'
'lib/GLib/Uri.pm6'
so I guess your modules won't work on MacOS. period :-( 09:28
09:54 finanalyst joined
ab5tract Oh yeah… that’s such a WAT on macOS 10:17
Though one might argue that the library is being a bit obtuse here, as well. I’m not sure how an end user should choose between these two 10:18
10:34 finanalyst left
Geth rakudo/main: 66c4acad2c | (Elizabeth Mattijsen)++ | 4 files
RakuAST: =place requires a URL in its specification

This was previously missed in the =place implememnation.
  finanalyst++ for reporting and nudging		 11:42
ugexe Won’t work on windows either then 12:33
Actually maybe I’m misremember windows file system case insensitivity 12:34
12:51 finanalyst joined
ugexe "Windows (local) file systems, including NTFS, as well as FAT and variants, are case insensitive (normally)." 13:33
guess i was correct
[Tux] Rakudo v2024.04-79-g66c4acad2 (v6.d) on MoarVM 2024.04-4-gc1eedd502
csv-ip5xs0.263 - 0.276
csv-ip5xs-201.166 - 1.222
csv-parser1.556 - 1.589
csv-test-xs-200.143 - 0.144
test1.963 - 2.015
test-t0.426 - 0.429
test-t --race0.277 - 0.299
test-t-205.377 - 5.382
test-t-20 --race1.284 - 1.336
 14:38
17:06 finanalyst left
jdv where the graphs again? i don't know why i can't google them:( 18:12
lizmat tux.nl/Talks/CSV6/speed.log 18:24
jdv i thought there were graphs. i guess i could remeber how to gnuplot or soemthing on that. 18:56
hasn't really moved lately it seems 19:18
imgur.com/a/evvgkBr 19:21
lizmat: thanks 19:22
ab5tract any idea where I can find the code that actually does the dumping of QAST for --target=[q]ast ? 19:35
I'd like to add it to the nqp edition of `dd` 19:36
MasterDuke i think src/HLL/Com(mandLine|piler).nqp in nqp. but not 100% sure on that 19:38
ab5tract ah, it was in the Compiler.nqp you mentioned, thanks MasterDuke 19:42
MasterDuke np 19:43
ab5tract do we have a quick way for a user to disable worries? 21:48
iirc they don't dispatch through the regular exception path, so you can't just catch them 21:49
Geth rakudo/r5175: 4e5bb8fb57 | ab5tract++ | 3 files
Add worry for WhateverCode on LHS of smartmatch

Smartmatch only curries `Whatever`, so any user that provides a `WhateverCode` expression as an LHS is likely to encounter a surprising failure (when compared to the behavior of most other infix operaators).
In order to be proactive and helpful to such users, we emit a descriptive worry in this scenario.		 21:53
rakudo: ab5tract++ created pull request #5564:
Add worry for WhateverCode on LHS of smartmatch		 21:54
ab5tract dangit, a typo... here comes another round of Geth 21:55
Geth rakudo/r5175: 9078c4dc21 | ab5tract++ | 3 files
Add worry for WhateverCode on LHS of smartmatch

Smartmatch only curries `Whatever`, so any user that provides a `WhateverCode` expression as an LHS is likely to encounter a surprising failure (when compared to the behavior of most other infix operaators).
In order to be proactive and helpful to such users, we emit a descriptive worry in this scenario.		 21:57
ab5tract third time is the charm.. 21:58
Geth rakudo/r5175: cb33a2b5ff | ab5tract++ | 3 files
Add worry for WhateverCode on LHS of smartmatch

Smartmatch only curries `Whatever`, so any user that provides a `WhateverCode` expression as an LHS is likely to encounter a surprising failure (when compared to the behavior of most other infix operaators).
In order to be proactive and helpful to such users, we emit a descriptive worry in this scenario.
ab5tract my only remaining confusion in all of this is why `*.(5)` doesn't curry here: 22:20
m: with -> Int $i { $i } { *.(5) == 5 ?? say "yeah" !! say "no" }
camelia No such method 'CALL-ME' for invocant of type 'Whatever'
in block <unit> at <tmp> line 1
ab5tract m: with -> Int $i { $i } { $_.(5) == 5 ?? say "yeah" !! say "no" }
camelia yeah
ab5tract m: with -> Int $i { $i } { dd $_.(5) } 22:21
camelia 5
ab5tract m: with -> Int $i { $i } { dd*.(5) }
camelia WARNINGS for <tmp>:
Useless use of "*" in expression "dd*.(5)" in sink context (line 1)
block (;; $_ is raw)
Use of Nil in numeric context
in block at <tmp> line 1
ab5tract m: with -> Int $i { $i } { dd *.(5) }
camelia No such method 'CALL-ME' for invocant of type 'Whatever'
in block <unit> at <tmp> line 1
ab5tract my confusion is based on my pre-existing general rule of thumb that dispatching a method on a Whatever is a sure-fire way to get a WhateverCode 22:22
sanity checking on the above: 22:50
m: with "lol" { say *.uc eq "Lol" ?? "yo" !! "no" }
camelia yo
23:37 sena_kun left

Powered by Cro and the Raku® Programming Language.

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

Thank you!