[00:04] <Geth> ¦ rakudo/main: 06a427938d | (Nick Logan)++ (committed using GitHub Web editor) | 5 files

[00:04] <Geth> ¦ rakudo/main: RakuAST: let BEGIN-time code in an EVAL see the context around the EVAL (#6800)

[00:04] <Geth> ¦ rakudo/main: 

[00:04] <Geth> ¦ rakudo/main: Previously code run at BEGIN time of an EVAL, or of a REPL line, could

[00:04] <Geth> ¦ rakudo/main: only see the lexicals around that EVAL which it named itself. Such code

[00:04] <Geth> ¦ rakudo/main: runs in a frame whose outer is the setting, so a nested `EVAL q{Foo}`

[00:04] <Geth> ¦ rakudo/main: or a `::('Foo')` there failed for a `Foo` declared around the EVAL. The

[00:04] <Geth> ¦ rakudo/main: legacy frontend finds it.

[00:04] <Geth> ¦ rakudo/main: <…commit message has 16 more lines…>

[00:04] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/06a427938d

[00:08] <Geth> ¦ rakudo: ugexe++ created pull request #6803: RakuAST: share the EXPORT package of the code an EVAL is compiled in

[00:08] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6803

[01:00] <Geth> ¦ rakudo/main: dd4af839dc | (Nick Logan)++ | 4 files

[01:00] <Geth> ¦ rakudo/main: RakuAST: let an EVAL run during another compilation export

[01:00] <Geth> ¦ rakudo/main: 

[01:00] <Geth> ¦ rakudo/main: Previously `is export` died with "No such method 'stubbed-meta-object'"

[01:00] <Geth> ¦ rakudo/main: in an EVAL compiled while another compilation runs, as a `BEGIN EVAL`

[01:00] <Geth> ¦ rakudo/main: does. The package such an EVAL takes from its context went onto the

[01:00] <Geth> ¦ rakudo/main: resolver's package stack as a plain constant declaration, and exporting

[01:00] <Geth> ¦ rakudo/main: asks every package there for its meta-object.

[01:00] <Geth> ¦ rakudo/main: <…commit message has 6 more lines…>

[01:00] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/dd4af839dc

[01:00] <Geth> ¦ rakudo/main: 8aa1b7d190 | (Nick Logan)++ | 8 files

[01:00] <Geth> ¦ rakudo/main: RakuAST: share the EXPORT package of the code an EVAL is compiled in

[01:00] <Geth> ¦ rakudo/main: 

[01:00] <Geth> ¦ rakudo/main: Previously every EVAL, and every REPL line, started a fresh EXPORT

[01:00] <Geth> ¦ rakudo/main: package. A `sub foo is export` in an EVAL was exported into a package

[01:00] <Geth> ¦ rakudo/main: that nothing around the EVAL could see. A bare `EXPORT` in the EVAL

[01:00] <Geth> ¦ rakudo/main: found the EXPORT package of the code around it, while

[01:00] <Geth> ¦ rakudo/main: `EXPORT::DEFAULT::<&foo>`, `::('EXPORT')` in its BEGIN-time code, and

[01:00] <Geth> ¦ rakudo/main: <…commit message has 14 more lines…>

[01:00] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/8aa1b7d190

[01:00] <Geth> ¦ rakudo/main: aa607786bb | (Nick Logan)++ (committed using GitHub Web editor) | 11 files

[01:00] <Geth> ¦ rakudo/main: Merge pull request #6803 from ugexe/ugexe/rakuast-eval-shared-export

[01:00] <Geth> ¦ rakudo/main: 

[01:01] <Geth> ¦ rakudo/main: RakuAST: share the EXPORT package of the code an EVAL is compiled in

[01:01] <Geth> ¦ rakudo/main: review: https://github.com/rakudo/rakudo/commit/aa607786bb

[01:25] <[Coke]> 88626a3 is clear except for Injector.

[01:26] <[Coke]> pushed latest output to repo