IRCloggy #raku-dev 2019-10-14

Logs Search ←Prev date Next date→ Channels Documentation

Provider of IRC logs since 2005.
WARNING: As Freenode became unjoinable and lost all warnings in topics, we cannot log channels on Freenode anymore.

2019-10-14

→ AlexDani` joined01:24
← AlexDaniel left01:28
AlexDani` → AlexDaniel11:30
← AlexDaniel left11:30
→ AlexDaniel joined11:30
→ tbrowder joined12:07
tbrowder hi, #raku-dev people!12:07
→ MasterDuke joined12:30
→ Geth__ joined12:34
AlexDaniel ok, this is just a test12:34
→ Geth_ joined12:47
← Geth__ left12:47
Geth_ ¦ rakudo: 6f086e65ee | (Aleks-Daniel Jakimenko-Aleksejev)++ | README.md12:48
¦ rakudo: Initial Raku changes to the README 12:48
¦ rakudo:12:48
¦ rakudo: Other things will need to be adjusted later.12:48
¦ rakudo: review: https://github.com/rakudo/rakudo/commit/6f086e65ee12:48
lizmat AlexDaniel: so, do you plan on the next release being a Raku release ?12:49
→ tyil joined12:51
AlexDaniel lizmat: it won't be a “Rakudo Perl 6” release for sure, it'll be just a “Rakudo” release12:52
and more changes will be done, I think. “Rakudo is an implementation of Raku on the Moar Virtual Machine”12:53
lizmat ack, ok12:53
AlexDaniel so yes, I think it'll be a Raku release, I don't see an easy way for it to be not12:54
→ tobs joined13:15
→ nine joined13:23
→ patrickb joined13:31
Geth_ ¦ problem-solving: d9beab8df7 | (Aleks-Daniel Jakimenko-Aleksejev)++ | 6 files13:31
¦ problem-solving: Consistify filenames 13:31
¦ problem-solving:13:31
¦ problem-solving: The idea is that existing files in the repo define how new files13:31
¦ problem-solving: should look like, so it's a good idea to keep files consistent. The13:31
¦ problem-solving: first document had spaces in it, which I guess can be a problem13:31
¦ problem-solving: sometimes, so kebab-case it is then.13:31
¦ problem-solving: review: https://github.com/perl6/problem-solving/commit/d9beab8df713:31
→ ZzZombo joined13:33
Geth_ ¦ roast: vrurg self-assigned Renaming of Perl6 to Raku https://github.com/perl6/roast/issues/58213:44
→ bartolin joined13:51
← Kaiepi left14:02
→ Kaiepi joined14:02
Geth_ ¦ rakudo: usev6++ created pull request #3231: Detect non-native literal passed in when rw container is expected 15:12
¦ rakudo: review: https://github.com/rakudo/rakudo/pull/323115:12
← patrickb left15:21
→ zostay joined15:21
→ rba joined15:26
→ patrickb joined15:53
← Kaiepi left16:00
→ Kaiepi joined16:02
→ rba[m] joined16:46
→ lucasb joined17:25
← feb left17:36
→ SyrupThinker joined17:52
→ leont joined18:08
Geth_ ¦ nqp: 764fe670d8 | (Aleks-Daniel Jakimenko-Aleksejev)++ | tools/templates/MOAR_REVISION18:27
¦ nqp: [MoarVM Bump] 56fa7a0cc Refer to Rakudo as jus […] 18:27
¦ nqp:18:27
¦ nqp: MoarVM bump brought: https://github.com/MoarVM/MoarVM/compare/2019.07.1-265-g95f69be84...2019.07.1-266-g56fa7a0cc18:27
¦ nqp: review: https://github.com/perl6/nqp/commit/764fe670d818:27
¦ rakudo: f3dda96a8b | (Aleks-Daniel Jakimenko-Aleksejev)++ | tools/templates/NQP_REVISION18:27
¦ rakudo: [NQP Bump] Brings 2 commits 18:27
¦ rakudo:18:27
¦ rakudo: NQP bump brought: https://github.com/perl6/nqp/compare/2019.07.1-145-g47af9d8a9...2019.07.1-147-g764fe670d18:27
¦ rakudo: 764fe670d [MoarVM Bump] 56fa7a0cc Refer to Rakudo as jus […]18:27
¦ rakudo: 2051967f2 Some Raku changes18:27
¦ rakudo: review: https://github.com/rakudo/rakudo/commit/f3dda96a8b18:27
→ sortiz joined18:34
→ ufobat joined19:10
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
← Kaiepi left19:38
→ Kaiepi joined19:39
→ ufobat_ joined19:42
vrurg patrickb: what do you mean by 'disturbed'?19:43
patrickb not being usable.19:43
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
← ufobat left19: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
ufobat_ → ufobat19:53
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()19:58
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 am20:22
sortiz Thank you20:28
MasterDuke would this be relevant for rakudo (or moarvm)? https://tokio.rs/blog/2019-10-scheduler/20:41
nine Cloning may be an issue20:43
← Kaiepi left21:02
→ Kaiepi joined21:03
← Kaiepi left21:04
→ Kaiepi joined21:05
→ titsuki joined22:16
← patrickb left22:45
← sortiz left22:47
Geth_ ¦ nqp: vrurg++ created pull request #584: Produce better error message when callee is not found 22:54
¦ nqp: review: https://github.com/perl6/nqp/pull/58422:54
vrurg Does nqp::p6capturelex ought to capture the setting too?22:59

Logs Search ←Prev date Next date→ Channels Documentation