🦋 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.
Geth rakudo: vrurg++ created pull request #5003:
Fix some cases of coercion over containerized values
01:53
vrurg jdv: what kind of issue was it? I remember no details on this. 01:56
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
02:57
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
japhb vrurg: Confirmed that gives a clean build, Getopt::Long too. :-) 07:08
SmokeMachine jdv: yes, I think lizmat has fixed that: irclogs.raku.org/raku-dev/2022-06-08.html#13:39 07:58
Geth JSON-Unmarshal/main: b500bfa329 | (Elizabeth Mattijsen)++ | 2 files
0.11
08:26
[Coke] patrickb: (rakuw) not in particular no. I'm a windows user, but not a power user. 13:20
Geth JSON-Unmarshal/main: 4 commits pushed by (Jonathan Stowe)++, (Elizabeth Mattijsen)++, (Vadim Belman)++ 13:28
patrickb [Coke]: So you can't reproduce either? 13:47
lizmat and yet another Rakudo Weekly News hits the Net: rakudoweekly.blog/2022/07/25/2022-30-what/ 14:01
jdv SmokeMachine: ok. just to confirm - you're good on HEAD now? 14:51
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
[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
Geth rakudo/lizmat-died-naturally: eb731f7355 | (Elizabeth Mattijsen)++ | src/main.nqp
s/DIED-NATURALLY/DIED/

Indeed. Any other way to finish a program, is by not die-ing :-)
18:03
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 (???)
jdv lizmat: so you know. changes are probably for the best. 21:00
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
bisectable6 lizmat, and I oop! Backtrace: gist.github.com/f2a65e8dcce52c8774...0cfbe51aaf 22:14
lizmat meh 22:15
first in 2020.05 I believe
sleep&
Kaiepi LAPTOP-7I9RCT0C% nqp-j -e 'nqp::barrierfull()' 23:48
LAPTOP-7I9RCT0C%
partway there...
there's a way to do this without dumping more warnings in logs