In the old design the COMPILING is described at https://github.com/Raku/old-design-docs/blob/master/S02-bits.pod#the-compiling-pseudopackage
The COMPILING PseudoStash currently allows assignments at runtime:
$ raku -e 'COMPILING::<foo> = 42; dd COMPILING::<foo>'
42
There are also some TODOed tests in roast, specifically in t/spec/S04-declarations/constant.t.
There is no mention of the COMPILING PseudoStash in the ecosystem that I could find.
All in all it feels like something that turned out to not really be needed, as the Rakudo compiler has been able to all of the things that were described in the design without actually needing to implement the COMPILING PseudoStash.
Feels to me that all references to COMPILING as a PseudoStash can be removed from Rakudo and roast.
In the old design the
COMPILINGis described at https://github.com/Raku/old-design-docs/blob/master/S02-bits.pod#the-compiling-pseudopackageThe
COMPILINGPseudoStashcurrently allows assignments at runtime:There are also some TODOed tests in roast, specifically in t/spec/S04-declarations/constant.t.
There is no mention of the
COMPILINGPseudoStashin the ecosystem that I could find.All in all it feels like something that turned out to not really be needed, as the Rakudo compiler has been able to all of the things that were described in the design without actually needing to implement the
COMPILINGPseudoStash.Feels to me that all references to
COMPILINGas aPseudoStashcan be removed from Rakudo and roast.