| Geth | rakudo/main: 06a427938d | (Nick Logan)++ (committed using GitHub Web editor) | 5 files RakuAST: let BEGIN-time code in an EVAL see the context around the EVAL (#6800) Previously code run at BEGIN time of an EVAL, or of a REPL line, could only see the lexicals around that EVAL which it named itself. Such code runs in a frame whose outer is the setting, so a nested `EVAL q{Foo}` or a `::('Foo')` there failed for a `Foo` declared around the EVAL. The legacy frontend finds it. ... (16 more lines) |
00:04 | |
| rakudo: ugexe++ created pull request #6803: RakuAST: share the EXPORT package of the code an EVAL is compiled in |
00:08 | ||
| rakudo/main: dd4af839dc | (Nick Logan)++ | 4 files RakuAST: let an EVAL run during another compilation export Previously `is export` died with "No such method 'stubbed-meta-object'" in an EVAL compiled while another compilation runs, as a `BEGIN EVAL` does. The package such an EVAL takes from its context went onto the resolver's package stack as a plain constant declaration, and exporting asks every package there for its meta-object. ... (6 more lines) |
01:00 | ||
| rakudo/main: 8aa1b7d190 | (Nick Logan)++ | 8 files RakuAST: share the EXPORT package of the code an EVAL is compiled in Previously every EVAL, and every REPL line, started a fresh EXPORT package. A `sub foo is export` in an EVAL was exported into a package that nothing around the EVAL could see. A bare `EXPORT` in the EVAL found the EXPORT package of the code around it, while `EXPORT::DEFAULT::<&foo>`, `::('EXPORT')` in its BEGIN-time code, and ... (14 more lines) |
|||
| rakudo/main: aa607786bb | (Nick Logan)++ (committed using GitHub Web editor) | 11 files Merge pull request #6803 from ugexe/ugexe/rakuast-eval-shared-export RakuAST: share the EXPORT package of the code an EVAL is compiled in |
|||
| [Coke] | 88626a3 is clear except for Injector. | 01:25 | |
| pushed latest output to repo | 01:26 |