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
Replace $?UNICODE-VERSION
by Unicode.version
#5191
Conversation
lizmat
commented
Feb 6, 2023
- creates a Unicode class to keep info about Unicode versions
- add a Unicode.version class method with former $?UNICODE-VERSION value
- add a Unicode.NFG class method indicating support for NFG
- adapt tests accordingly
- creates a Unicode class to keep info about Unicode versions - add a Unicode.version class method with former $?UNICODE-VERSION value - add a Unicode.NFG class method indicating support for NFG - adapt tests accordingly
$?UNICODE-VERSION
by Unicode.version
This one I would still backport to 6.c. Not all code could easily be converted to the new version, which is anyway is still in PREVIEW state. And yet the feature is way too useful for many, I think. If not crucial sometimes. |
Disagree. If we would backport it, then you wouldn't know which release starts supporting it. And we have too much of that already. Also, if it was that crucial sometimes, why wasn't this done earlier? |
For some features/fixes I have compiler version check in my code. It is inevitable sometimes: die "Rakudo of at least v2019.11 required to run this version of " ~ ::?PACKAGE.^name
unless $*RAKU.compiler.version >= v2019.11;
Anyway, I would insist on having this one at 6.c level. It had to be there from the beginning. |
Ok, I tried moving the Unicode class into core.c
and moving the file from
I've now spent an hour trying to figure what is tickling this and am now giving up. |
I tried it locally, but inserted it after |
Implemented as db7ca2dd03 |