Mostly working on the Raku Programming Language. Born at 314 ppm.
Raku @programming.dev Definitely How What Where, Who? - Elizabeth Mattijsen
Raku @programming.dev Raku Resolutions #3 - Elizabeth Mattijsen
Raku @programming.dev Store Proxy Fetch - Elizabeth Mattijsen
Raku @programming.dev Method Not Found Fallback - Elizabeth Mattijsen
Raku @programming.dev Enumerating in RakuDoc v2 - Richard Hainsworth
Raku @programming.dev Associative Methods - Elizabeth Mattijsen
Raku @programming.dev Positional Methods - Elizabeth Mattijsen
Raku @programming.dev The second two - Raku Resolutions
Raku @programming.dev Tweak Build - Elizabeth Mattijsen
Raku @programming.dev Two Bugs, One Symptom - Waclaw Kusnierczyk
Raku @programming.dev Doc Mirages - Elizabeth Mattijsen
Raku @programming.dev Catch Control - Elizabeth Mattijsen
Raku @programming.dev Last Close, and Quitting - Elizabeth Mattijsen
Raku @programming.dev First Next, then Last - Elizabeth Mattijsen
Raku @programming.dev Hello, Goodbye - Elizabeth Mattijsen
Raku @programming.dev INIT to an END - Elizabeth Mattijsen
Raku @programming.dev Cases of UPPER - Elizabeth Mattijsen
Raku @programming.dev Cases of UPPER - Elizabeth Mattijsen
Raku @programming.dev The first four - Elizabeth Mattijsen
Raku @programming.dev RakuDoc - More than just a documentation markup - Richard Hainsworth


















Well, I would agree with regards to PRE and POST. But ENTER / LEAVE are used a lot, and KEEP / UNDO most certainly as well by database oriented modules such as Red. There are 62 modules that use ENTER in the ecosystem, and 262 that use LEAVE. So definitely not obscure in Raku.
I guess one of the reasons for LEAVE being used as much, is because Raku doesn't have timely destruction (whereas Perl does).