We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrated from rt.perl.org#130186 (status was 'resolved')
Searchable as RT130186$
The text was updated successfully, but these errors were encountered:
*Code:* dd �789�.comb(/ . {say $/} <!> /)'
*Result:* ï½¢7ï½£ ï½¢7ï½£ ï½¢7ï½£ slip()
It may seem like it is stuck on �7� and does not progress at all. However, if we add parens around . we will get this:
*Code:* dd �789�.comb(/ (.) {say $/} <!> /)
*Result:* ï½¢7ï½£ 0 => ï½¢7ï½£ ï½¢8ï½£ 0 => ï½¢8ï½£ ï½¢9ï½£ 0 => ï½¢9ï½£ slip()
I do not understand why the first snippet prints ï½¢7ï½£ three times.
Sorry, something went wrong.
This was fixed during the uncurse merge. Bisect log (20 candidates): https://gist.github.com/7cedc2e2e35913544f75bc5fc89bd088
ï½¢testneededï½£
On 2016-11-26 18:36:35, alex.jakimenko@gmail.com wrote:
*Code:* dd ‘789’.comb(/ . {say $/} <!> /)' *Result:* ï½¢7ï½£ ï½¢7ï½£ ï½¢7ï½£ slip() It may seem like it is stuck on ‘7’ and does not progress at all. However, if we add parens around . we will get this: *Code:* dd ‘789’.comb(/ (.) {say $/} <!> /) *Result:* ï½¢7ï½£ 0 => ï½¢7ï½£ ï½¢8ï½£ 0 => ï½¢8ï½£ ï½¢9ï½£ 0 => ï½¢9ï½£ slip() I do not understand why the first snippet prints ï½¢7ï½£ three times.
*Code:* dd ‘789’.comb(/ . {say $/} <!> /)'
It may seem like it is stuck on ‘7’ and does not progress at all. However, if we add parens around . we will get this:
*Code:* dd ‘789’.comb(/ (.) {say $/} <!> /)
Test added: Raku/roast@005b4f76f7
@moritz - Status changed from 'new' to 'resolved'
No branches or pull requests
Migrated from rt.perl.org#130186 (status was 'resolved')
Searchable as RT130186$
The text was updated successfully, but these errors were encountered: