| 27 Jul 2026 | |||
| notable6 | lizmat, 9 notes: gist.github.com/7068c966fd23d468d5...c61c075098 | 10:43 | |
| lizmat | notable6: weekly reset | 10:55 | |
| notable6 | lizmat, Moved existing notes to “weekly_2026-07-27T10:55:04Z” | ||
| lizmat | And another Rakudo Weekl;y hits the Net: rakudoweekly.blog/2026/07/27/2026-...thank-you/ | 12:55 | |
| [Coke] | lizmat++ lizmat++ lizmat++ | 12:56 | |
| One nice feature that wasn’t really mentioned in the Rakudo 2026.07 announcement, were the general GDB plugin improvements for low-level (core) debugging, contributed by Timo Paulssen. Exciting stuff! | 12:58 | ||
| ... oops | |||
| lizmat | yeah, shit happens... it was a last minute addition :-) | ||
| [Coke] | Reading this - it was because we didn't do a separate bump so the commit showed up in rakudo *before* I started the release. | ||
| Sorry. Was not intentional, timo. | 12:59 | ||
| (and I remember saying "don't do a bump or revert" because I was still thinking about it a few days pre. | |||
| timo | I really should have waited until after the release to merge that. i'm not sure in retrospect why i thought it would be NBD | 13:12 | |
| hurufu | hurufu left | 13:17 | |
| finanalyst | finanalyst joined | 20:08 | |
| nine | nine left | 21:08 | |
| finanalyst | finanalyst left | 21:33 | |
| japhb | ... because hope springs eternal? :-) | 22:10 | |
| timo | my foolishness is boundless | 22:14 | |
| japhb | My cat's foolishness does a lot of bounding | 22:23 | |
| timo | yo japhb what would you have me put into the "omniscient debugger" parts of moar rrdb? | 22:28 | |
| Voldenet | yay new weekly | 22:33 | |
| japhb | timo: Hmmm, good question. Maybe some way to track the movement of data through the moar-level pieces of Supplies and Channels? I would think each would be interesting for different reasons: Supplies turning into a tree traversal, Channels involving task switches, and both involving the scheduler. | 22:37 | |
| Part of the problem is (Supplies and Channels) feeding (Supplies and Channels). | 22:38 | ||
| If I'm tracing something backwards I'd like to follow it backwards through a Channel or Supply to where it was created, follow back whatever middleware computation is happening, and then back into the next Channel or Supply in the link. | 22:39 | ||
| With the problem that it's not entirely obvious what to do about the fact that running a Supply in reverse turns a 1:N traversal into an N:1 merge. | 22:40 | ||