[00:52] <Geth> ¦ rakudo: ugexe++ created pull request #6658: Apply :ratchet to an atom followed by sigspace whitespace

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

[00:53] <ugexe> [Coke]: any way you could do a blin run on https://github.com/rakudo/rakudo/pull/6658 ? I'm trying to see the fallout (as there is at least one: ASN::Grammar) to determine if its something we can even change at this point

[01:17] <[Coke]> I think we need to copy your branch to one on rakudo/rakudo, should be easy

[01:18] <[Coke]> on it

[01:20] <ugexe> thanks!

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: da2a52539d | (Nick Logan)++ | 4 files

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: Ratchet the atom under trailing sigspace

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: 

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: In a ratchet regex the whitespace that sigspace inserts after an atom was

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: attached inside the node the enclosing position ratchets, so the ratchet

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: landed on a concat, which the regex compiler ignores. A quantifier,

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: alternation, subrule call or capture group followed by whitespace in a

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: rule or an rx:r:s regex therefore backtracked as if there were no ratchet:

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: <…commit message has 24 more lines…>

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: review: https://github.com/rakudo/rakudo/commit/da2a52539d

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: b180d6078d | (Nick Logan)++ | t/02-rakudo/ltm-before-assertion.t

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: Backtrack explicitly in the LTM before-assertion test grammar

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: 

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: The lookahead in the test grammar's infix chain rule matched `.+` and then

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: an operator, with rule whitespace in between. A rule ratchets that

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: quantifier, so once it has taken the rest of the input it cannot give the

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: operator back, and the lookahead only succeeded while the whitespace after

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: the quantifier shielded it from the ratchet.

[01:21] <[Coke]> c: b180d6078d e.say # when this works I can blin run

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: 

[01:21] <committable6> [Coke], ¦b180d60: «Cannot find this revision (did you mean “7fb098d”?)»

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: This backtracks with `.+!` instead, which stays declarative for the LTM

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: prefix the test is about and matches under the ratchet.

[01:21] <Geth> ¦ rakudo/ugexe/rakuast-sigspace-ratchet: review: https://github.com/rakudo/rakudo/commit/b180d6078d

[01:37] <[Coke]> started

[01:37] <[Coke]> did it from 2026.08 so we also get the last few commits that weren't in the last run

[03:00] <[Coke]> ⏳ 1250 out of 2520 modules processed (49.6%)

[03:47] <Geth> ¦ rakudo: ugexe++ created pull request #6659: RakuAST: fix a batch of deparse holes found by round tripping raku code

[03:47] <Geth> ¦ rakudo: review: https://github.com/rakudo/rakudo/pull/6659

[04:46] *** kurahaupo joined