Skip to content

Instantly share code, notes, and snippets.

@ab5tract

ab5tract/pod.raku

Last active September 23, 2025 07:58
Show Gist options
  • Save ab5tract/538a991b64e43e544656799a0dee3fca to your computer and use it in GitHub Desktop.
Save ab5tract/538a991b64e43e544656799a0dee3fca to your computer and use it in GitHub Desktop.
Download ZIP
$=pod visibility
Raw
pod.raku
=for foo
zippo
say $=pod;
q:to/CODE/.EVAL;
say $=pod
CODE
Raw
zz.output-from-dev-branch
[Pod::Block::Named{:name("foo")}
Pod::Block::Para
zippo say $=pod;
]
@ab5tract
Copy link
Author

All output examples are produced with RAKUDO_RAKUAST=1

@lizmat
Copy link

lizmat commented Sep 23, 2025

The way I interpret the $= variables, is that they are compunit bound. Since EVALs are compunits, they should start with a fresh set of $= variables, and should not be able to see the outer $= variables.

So I'd say the dev branch is wrong in that respect.

Q: what happens in the dev branch if you add pod there? Does it get added to the outer $=pod ? Or does it replace it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment