| Geth | rakudo/main: 5c93e18bf9 | (Elizabeth Mattijsen)++ | src/core.c/Pair.rakumod Make for %h -> (:$key, :$value) { ... } 2x as fast github.com/rakudo/rakudo/issues/6053 finally got me grokking this idiom. What I hadn't realized before is that in the case of a sub-signature (as indicated by the parentheses) it will actually call the .Capture method on the object the iterator produced, and then try to bind that to the sub-signature. ... (9 more lines) |
19:01 | |
| rakudo/main: babc6ca406 | (Elizabeth Mattijsen)++ | src/core.c/Pair.rakumod Make for %h -> (:$key, :$value) { ... } another 5% faster By using nqp ops in Pair.Capture |
19:09 | ||
| lizmat | so I wonder whether it would make sense to actually automatically create a customized Capture method for classes at compose time, if they don't have a Capture method already that isn't Mu::Capture | 19:15 | |
| otoh, people playing these type of Capture tricks, would know what they were doing anyway... | 19:16 | ||
| Geth | rakudo/lizmat-comb-Cool: ac55cc6aaf | (Elizabeth Mattijsen)++ | src/core.c/Rakudo/Iterator.rakumod Make .comb accept Cool values for limit In response to github.com/rakudo/rakudo/issues/6030 So "foobar".comb(/\w/, 2.0) will produce ("f","o").Seq |
19:58 | |
| rakudo: lizmat++ created pull request #6083: Make .comb accept Cool values for limit |
19:59 | ||
|
19:59
finanalyst joined
21:36
finanalyst left
|
|||
| ab5tract | lizmat: thanks for digging into this! | 22:15 | |