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
Solved on MoarVM / Needs NFC support on JVM | Str.Int confused by diacritics #5418
Comments
From zefram@fysh.orgThe Str.Int coercion method is usually strict about the string content
But if the content is non-numeric only by having diacritics on the digits,
This is a bug. The "4\x[308]" grapheme (digit four with diaeresis, das This bug only shows up when the string otherwise consists solely -zefram |
From @zoffixznetQuestion for the [@LARRY] team: should this throw an error or silently ignore the diacritic? |
The RT System itself - Status changed from 'new' to 'open' |
From @zoffixznetOn Tue, 05 Jul 2016 08:34:51 -0700, zefram@fysh.org wrote:
Thanks for the report. The issue has been fixed on MoarVM. On JVM, we still need proper NFC support for this to work, so I'm leaving the ticket open as a JVM-only thing. Fixed in rakudo/rakudo@d540fc8 |
From @usev6On Fri, 11 Nov 2016 08:57:19 -0800, cpan@zoffix.com wrote:
The test in S32-str/numeric.t actually passes on JVM. I'm going to unfudge that test. I'm not sure whether there are other cases which do not work on JVM (due to missing NFC support) or whether this ticket can be closed. |
@zoffixznet - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#128542 (status was 'resolved')
Searchable as RT128542$
The text was updated successfully, but these errors were encountered: