03:27 apogee_ntv left 03:29 apogee_ntv joined
ab5tract anyone know whether it's by design that EVAL'd code can't access the doc variables of its outer scope? 07:34
lizmat shared this with me: gist.github.com/lizmat/69c4568c618...e18d1a270b
in my code the output looks like this: gist.github.com/ab5tract/538a991b6...9a0dee3fca 07:37
07:47 rakkable__ left 07:48 rakkable joined
lizmat ab5tract: left a comment 07:58
ab5tract lizmat: thanks!
The issue I'm having with the EVAL stuff is that when the EVAL CU visits its doc vars, I get re-declaration errors 08:00
I've got to run now but I'll get the output you mentioned in your comment this afternoon hopefully
Geth rakudo/r5855-finish-shenanigans: d69369f8f3 | ab5tract++ | 2 files
Broken :(
08:04
rakudo/r5855-finish-shenanigans: 912e74ebdc | ab5tract++ | 2 files
Only two test still failing
rakudo/r5855-finish-shenanigans: a3a12e753d | ab5tract++ | src/Raku/ast/code.rakumod
Still doc-declarator
ab5tract hmm, I thought it would have pushed to the open PR, I guess I made another branch
afk&
[Coke] ponders where to post a small update about getting us onboarded with Snyk, and guesses bluesky is fine? 12:59
lizmat dev.to ? 13:02
releasable6 Next release in ≈4 days and ≈3 hours. There are no known blockers. Please log your changes in the ChangeLog: github.com/rakudo/rakudo/wiki/ChangeLog-Draft 15:00
[Coke] That is not true. 16:03
Might need to update the "next release date" in the release guide. 16:07
Geth rakudo/main: 86d216d3fa | Coke++ | docs/release_guide.pod
No release this month
16:22
[Coke] releasable6: next
releasable6 [Coke], Next release in ≈4 days and ≈2 hours. There are no known blockers. 0 out of 6 commits logged 16:23
[Coke], Details: gist.github.com/371113f6b9647665b2...e5ebaac110
[Coke] let's see if that updates in the next hour or so
releasable6: next 16:30
releasable6 [Coke], Next release in ≈25 days and ≈2 hours. There are no known blockers. 0 out of 7 commits logged
[Coke], Details: gist.github.com/e02c2766f608ba18db...7e35bb28c3
19:00 vrurg_ left 19:02 vrurg joined
[Coke] github.com/rakudo/docker/blob/mast...Dockerfile - why do we rename the dockerfile every release? 23:37
if we kept the historic ones it might make sense, but it looks like we create a new one and delete the old one. 23:40
(makes it slightly harder to deal with repository scanning - I just had to rescan to get the new ones, and then manually delete the old ones that had already been id'd by Snyk) 23:43