| Geth | Subsets-IO/ugexe/rakuast: 8c5cc3bd56 | (Nick Logan)++ | 3 files Use `use experimental :will-complain` directly The module detected the `will complain` trait by reaching into the used module's export packages with `::("EXPORT").WHO<will-complain>`, a workaround for the old precompilation issue rakudo#4933. This relied on `use experimental` rebinding the importer's own `EXPORT` symbol to experimental's EXPORT package, which the legacy frontend happens to do ... (14 more lines) |
20:27 | |
| Subsets-IO: ugexe++ created pull request #3: Use `use experimental :will-complain` directly |
|||
| Subsets-IO/main: 1b1f98fe73 | (Nick Logan)++ (committed using GitHub Web editor) | 3 files Use `use experimental :will-complain` directly The module detected the `will complain` trait by reaching into the used module's export packages with `::("EXPORT").WHO<will-complain>`, a workaround for the old precompilation issue rakudo#4933. This relied on `use experimental` rebinding the importer's own `EXPORT` symbol to experimental's EXPORT package, which the legacy frontend happens to do ... (14 more lines) |
22:14 | ||
| Pod-TreeWalker/ugexe/rakuast-test-fixes: 2aa4ccab31 | (Nick Logan)++ | 3 files Fix declarator and defn tests The attribute declarator test expected a WHEREFORE of Any. That only happened because the legacy frontend sets an attribute's WHEREFORE lazily when .WHY is called. The RakuAST frontend sets it up front. The test now expects the attribute itself on both. The defn test failed because TestListener did not handle Pod::Defn, so its contents were never walked. It also expected the defn to end before its paragraph. |
22:25 | ||
| Pod-TreeWalker: ugexe++ created pull request #13: Fix declarator and defn tests |
|||
| Subsets-IO/main: 2524d08867 | (Elizabeth Mattijsen)++ | 15 files CI test prior to release |
22:36 | ||
| Subsets-IO/main: 6d3c5cc6a1 | (Elizabeth Mattijsen)++ | 3 files 1.2 |
22:41 | ||
| Test-Stream/main: b241137065 | (Nick Logan)++ (committed using GitHub Web editor) | t/400-tap-formatter.rakutest Make reported-line test expectations frontend agnostic Previously t/400-tap-formatter.rakutest hardcoded the line numbers that Test::Stream::Formatter::TAP12 reports for failing tests. That number comes from a CallFrame captured while the mainline is still inside the multi-line test-formatter(...) call, and which line annotation is active at that point differs by compiler frontend: the legacy frontend reports ... (7 more lines) |
22:43 | ||
| Test-Stream/main: 80df9d1b8a | (Elizabeth Mattijsen)++ | 10 files CI test prior to release |
22:47 | ||
| Test-Stream/main: eb7476f27c | (Elizabeth Mattijsen)++ | 5 files 0.2 |
22:55 |