New issue
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
NFC and NFD objects no longer smartmatch as strings ("7\x[308]".NFD ~~ /^ \d+ $/) #5951
Comments
From @AlexDanielCode: Result (2015.12,2016.10): Result (2016.11,HEAD): Previously it worked with NFC objects as if they were strings, which intuitively makes sense. However, I'm not going to claim that this is what it should do, I'm just pointing out that the behavior was changed. Right now it works with the .ord of the first character, this is probably less than awesome. The change is a result of both rakudo/rakudo@05b65d0 and rakudo/rakudo@33eeb32 |
From @lizmatFixed with 8d35951 , tests needed
|
The RT System itself - Status changed from 'new' to 'open' |
From @usev6Unfortunately commit 8d35951 breaks the build on JVM. It dies during stage parse with Error while compiling, type X::Parameter::InvalidType Type Uni is not usable with rakudo-j: $ perl6-j -e 'my Uni $foo' I'd suggest to add a special case for jvm, so that fix from commit 8d35951 is not applied there. I opened a PR for that: rakudo/rakudo#980 |
1 similar comment
From @usev6Unfortunately commit 8d35951 breaks the build on JVM. It dies during stage parse with Error while compiling, type X::Parameter::InvalidType Type Uni is not usable with rakudo-j: $ perl6-j -e 'my Uni $foo' I'd suggest to add a special case for jvm, so that fix from commit 8d35951 is not applied there. I opened a PR for that: rakudo/rakudo#980 |
From @moritzTested in https://rt-archive.perl.org/perl6//Public/Bug/Display.html?id=130458 Note that this is still not perfect, for example $/.orig doesn't contain an NFD after the match, but that's not in the scope of this ticket. |
@moritz - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#130458 (status was 'resolved')
Searchable as RT130458$
The text was updated successfully, but these errors were encountered: