🦋 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.
00:08 reportable6 left 00:09 reportable6 joined 00:38 [Coke] left 00:42 [Coke] joined
Geth rakudo: vrurg++ created pull request #5003:
Fix some cases of coercion over containerized values
vrurg jdv: what kind of issue was it? I remember no details on this. 01:56
02:21 evalable6 left, linkable6 left 02:23 linkable6 joined 02:24 evalable6 joined
jdv iirc it was related to your changes 02:47
the reason for this: github.com/FCO/Red/commit/bdd5bbdf...b9a726fb2a 02:53
vrurg: ^
SmokeMachine: do you know if thats fixed yet? 02:54
vrurg I'm afraid, more input would be needed. Vaguely recall that there was an issue opened, wasn't it? 02:56
Geth rakudo: fbe3acd007 | (Vadim Belman)++ | 2 files
Fix some cases of coercion over containerized values

  - The dispatcher itself never expects a containerized coercer, but it
   was possible for the metamodel to bypass a container
  - The scalar case of value was considerd, but `Proxy` has been
   overlooked; if there be any other kind of container it should be
   handled appropriately too
rakudo: 02f32d510b | (Vadim Belman)++ | src/vm/moar/dispatchers.nqp
Remove now unused 'raku-coerce' dispatcher

It was part of the old return value coercion implementation.
rakudo: aa5e680052 | (Vadim Belman)++ (committed using GitHub Web editor) | 2 files
Merge pull request #5003 from vrurg/rakudo-5002

Fix some cases of coercion over containerized values
03:24 linkable6 left, evalable6 left 03:27 linkable6 joined, evalable6 joined 04:16 vrurg left 04:17 vrurg joined 05:04 jjatria left, jjatria joined 05:07 tailgate left, bartolin_ left, JRaspass left, bartolin joined 05:08 JRaspass joined 05:09 tailgate joined 06:07 reportable6 left 06:09 reportable6 joined
japhb vrurg: Confirmed that gives a clean build, Getopt::Long too. :-) 07:08
07:09 evalable6 left, linkable6 left 07:11 evalable6 joined 07:12 linkable6 joined 07:51 sena_kun joined 07:54 ab5tract joined 07:56 sena_kun left 07:57 sena_kun joined
SmokeMachine jdv: yes, I think lizmat has fixed that: irclogs.raku.org/raku-dev/2022-06-08.html#13:39 07:58
08:18 jdv left 08:24 jdv joined
Geth JSON-Unmarshal/main: b500bfa329 | (Elizabeth Mattijsen)++ | 2 files
08:58 ab5tract left 09:17 sena_kun left 10:01 sena_kun joined 10:05 Kaiepi left 10:07 Kaiepi joined 11:07 evalable6 left, linkable6 left 11:09 evalable6 joined 11:10 linkable6 joined 12:06 reportable6 left 12:07 [Coke] left 12:09 reportable6 joined 12:11 Xliff left 12:27 [Coke] joined
[Coke] patrickb: (rakuw) not in particular no. I'm a windows user, but not a power user. 13:20
13:27 evalable6 left, linkable6 left
Geth JSON-Unmarshal/main: 4 commits pushed by (Jonathan Stowe)++, (Elizabeth Mattijsen)++, (Vadim Belman)++ 13:28
13:30 linkable6 joined, evalable6 joined
patrickb [Coke]: So you can't reproduce either? 13:47
13:54 Xliff joined
lizmat and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2022/07/25/2022-30-what/ 14:01
14:28 sena_kun left, Altai-man joined
jdv SmokeMachine: ok. just to confirm - you're good on HEAD now? 14:51
14:57 melezhik joined
releasable6 Next release in ≈4 days and ≈3 hours. 1 blocker. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 15:00
[Coke] patrickb: if it was the behavior I reported, nothing has changed. 15:08
patrickb [Coke]: How do you run `rakuw -e 'say 3'`? 15:11
Typing that into a Windows Terminal Window on my end outputs nothing. 15:12
15:20 melezhik left 16:22 patrickb left 16:27 patrickb joined 16:34 patrickb left 16:36 patrickb joined 17:06 Altai-man left 17:21 patrickb left 17:22 patrickb joined
[Coke] patrickb: ah. different behavior in git bash vs. cmd 17:27
makes sense, I probably had git bash open by default.
patrickb [Coke]: I guess all is fine then. :) 17:34
17:42 sena_kun joined 17:51 lizmat_ joined 17:52 discord-raku-bot left 17:53 gfldex left 17:55 lizmat left, Xliff left 18:00 lizmat_ is now known as lizmat
Geth rakudo/lizmat-died-naturally: eb731f7355 | (Elizabeth Mattijsen)++ | src/main.nqp

Indeed. Any other way to finish a program, is by not die-ing :-)
18:06 reportable6 left 18:09 reportable6 joined 18:55 sena_kun left 18:56 sena_kun joined
Voldenet Other way to finish a program is to inject exit syscall to it 19:05
> gdb -p "$1" -batch -ex 'set {short}$rip = 0x050f' -ex 'set $rax=231' -ex 'set $rdi=0' -ex 'cont' 19:06
(copied from gist.github.com/moyix/95ca9a7a26a6...c7411dc3be )
Kaiepi apparently this is how you fence in java? openjdk.org/jeps/171 19:27
atomic ints are ok, but fencing is Unsafe (???)
19:49 sena_kun left 19:50 sena_kun joined 20:25 vrurg left
jdv lizmat: so you know. changes are probably for the best. 21:00
21:14 discord-raku-bot joined 21:20 discord-raku-bot left, discord-raku-bot joined 21:27 gfldex joined 21:28 discord-raku-bot left 21:29 discord-raku-bot joined 21:38 kjp joined 21:41 sena_kun left
lizmat jdv? 21:49
bisectable6: old=2019.11 say Date.new('2015-11-24').last-date-in-month; 22:11
bisectable6 lizmat, On both starting points (old=2019.11 new=aa5e680) the exit code is 1 and the output is identical as well
lizmat, Output on both points: «4===SORRY!4=== Error while compiling /tmp/XZJSQJxlY6␤Confused␤at /tmp/XZJSQJxlY6:1␤------> 3say http:8⏏4//Date.new('2015-11-24').last-date-in-mo␤ expecting any of:␤ colon pair␤»
lizmat bisectable6: old=2019.11 say Date.new('2015-11-24').last-date-in-month; 22:12
bisectable6 lizmat, Bisecting by exit code (old=2019.11 new=aa5e680). Old exit code: 1
22:12 vrurg joined
bisectable6 lizmat, and I oop! Backtrace: gist.github.com/f2a65e8dcce52c8774...0cfbe51aaf 22:14
lizmat meh 22:15
first in 2020.05 I believe
22:33 discord-raku-bot left, discord-raku-bot joined 22:39 melezhik joined 22:56 melezhik left 23:12 maettu left 23:38 maettu joined
Kaiepi LAPTOP-7I9RCT0C% nqp-j -e 'nqp::barrierfull()' 23:48
partway there...
there's a way to do this without dumping more warnings in logs