Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Match.caps is inconsistent across backends #3753
19:57 <psch> j: say ("a" ~~ /<alpha> & <ident> & <alnum>/).caps
I'm not sure what the correct result would be. S05 mentions that there should be a warning with overlapping bindings. Additionally, sorting of captures is supposed to be by the sub-Matches .from, but it's not clarified what happens to elements with the value for .from. In any case, the current behavior makes at least a few tests S05-capture/caps.t underspecific, e.g.
not ok 36 - .caps & - multiple terms# TODO & caps on jvm
# Failed test '.caps & - multiple terms'
As of today (2017.11,HEAD(e5b660e)) it prints a *third* variant:
(ident => ｢a｣ alpha => ｢a｣ alnum => ｢a｣)
The change happened in (2017-02-22) rakudo/rakudo@1cafc67
To me it tells that it is just random.
On 2015-03-22 13:02:12, firstname.lastname@example.org wrote: