tbrowder hi, #raku-dev people! 12:07
AlexDaniel ok, this is just a test 12:34
Geth_ rakudo: 6f086e65ee | (Aleks-Daniel Jakimenko-Aleksejev)++ | README.md
Initial Raku changes to the README

Other things will need to be adjusted later.
12:48
lizmat AlexDaniel: so, do you plan on the next release being a Raku release ? 12:49
AlexDaniel lizmat: it won't be a “Rakudo Perl 6” release for sure, it'll be just a “Rakudo” release 12:52
and more changes will be done, I think. “Rakudo is an implementation of Raku on the Moar Virtual Machine” 12:53
lizmat ack, ok
AlexDaniel so yes, I think it'll be a Raku release, I don't see an easy way for it to be not 12:54
Geth_ problem-solving: d9beab8df7 | (Aleks-Daniel Jakimenko-Aleksejev)++ | 6 files
Consistify filenames

The idea is that existing files in the repo define how new files should look like, so it's a good idea to keep files consistent. The first document had spaces in it, which I guess can be a problem sometimes, so kebab-case it is then.
13:31
Geth_ ¦ roast: vrurg self-assigned Renaming of Perl6 to Raku github.com/perl6/roast/issues/582 13:44
Geth_ rakudo: usev6++ created pull request #3231:
Detect non-native literal passed in when rw container is expected
15:12
Geth_ nqp: 764fe670d8 | (Aleks-Daniel Jakimenko-Aleksejev)++ | tools/templates/MOAR_REVISION
[MoarVM Bump] 56fa7a0cc Refer to Rakudo as jus […]

MoarVM bump brought: github.com/MoarVM/MoarVM/compare/2...g56fa7a0cc
18:27
rakudo: f3dda96a8b | (Aleks-Daniel Jakimenko-Aleksejev)++ | tools/templates/NQP_REVISION
[NQP Bump] Brings 2 commits

NQP bump brought: github.com/perl6/nqp/compare/2019....g764fe670d 764fe670d [MoarVM Bump] 56fa7a0cc Refer to Rakudo as jus […] 2051967f2 Some Raku changes
patrickb Are gdb / valgrind / lldb disturbed by the process to be debugged exec-ing? 19:27
If yes, we could either change the gdb / valgrind / lldb runners to call the perl6-m native executable in the build directory or just remove them entirely. 19:35
vrurg patrickb: what do you mean by 'disturbed'? 19:43
patrickb not being usable.
vrurg patrickb: might be my English, but I don't get you. :) 19:44
patrickb the perl6-m executable in the build dir just execs moar with the correct parameters. The original reason the debugger wrapper scripts were added was because one couldn't debug a shell script. Now I replaced the shell script with a native executable. If those tools are working on that executable there is not much reason to keep them. 19:45
patrickb The only reason I can see why those tools might have a problem is because of the exec() that executable uses to call moar. 19:46
vrurg I see. Perhaps it didn't make sense to make them executables? Just have shortcuts for quick-start debug? 19:49
patrickb If `perl6-valgrind-m`ends up being a shortcut for `valgrind perl6-m` we can just remove it. It doesn't even save a single letter to type. 19:53
vrurg patrickb: I'll afk for a while. Will try to have another look at it later today if don't forget. 19:58
nine I think rr is not too happy about that exec()
patrickb nine: There is no rr wrapper atm though. 20:02
nine That's the irony :) 20:03
sortiz nine: If time permits, can you take a look to rakudo issue #3235 ? 20:20
nine sortiz: already am 20:22
sortiz Thank you 20:28
MasterDuke would this be relevant for rakudo (or moarvm)? tokio.rs/blog/2019-10-scheduler/ 20:41
nine Cloning may be an issue 20:43
Geth_ nqp: vrurg++ created pull request #584:
Produce better error message when callee is not found
22:54
vrurg Does nqp::p6capturelex ought to capture the setting too? 22:59