-
-
Notifications
You must be signed in to change notification settings - Fork 706
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
Upstream the Unicode database table generator and update the tables to 15 #8617
Conversation
|
Thanks for your pull request and interest in making D better, @rikkimax! We are looking forward to reviewing it, and you should be hearing from a maintainer soon.
Please see CONTRIBUTING.md for more information. If you have addressed all reviews or aren't sure how to proceed, don't hesitate to ping us with a simple comment. Bugzilla referencesYour PR doesn't reference any Bugzilla issue. If your PR contains non-trivial changes, please reference a Bugzilla issue or create a manual changelog. Testing this PR locallyIf you don't have a local development environment setup, you can use Digger to test this PR: dub run digger -- build "master + phobos#8617" |
|
Considering the size alone of this PR. I would welcome a somewhat long description of what this PR tries to do. |
The goal is to get the Unicode table generator into Phobos where it belongs. From what I can tell, it has never been updated and could be ~8 releases out of date. Unfortunately, people went messing with the tables since then, and not all changes got committed to the generator so it's not quite as simple as just adding it. The quality of the generator doesn't matter, nor do the tables themselves. As long as it passes the test suite we are good (Dmitry attempted to update the tables to 14 already, and this approach was the outcome of that). |
| string[string] aliases; | ||
| } | ||
|
|
||
| PropertyTable general; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
no need to make them thread-local, it bloats the TLS and its effectively global state.
|
@ljmf00 I didn't develop the generator, that was Dmitry Olshansky ~2013. Its quality does not matter as long as it works. If we do not get the generator into Phobos Right now I want to change as little as possible, it needs to work, beyond that it's out of scope of the PR. |
I didn't request changes tho, just suggestions :) Some |
All good, I just don't want people wasting their effort on this PR for code review, that stuff can come later once the harder unicode parts are resolved. I'm getting these errors, I'd love it if someone could verify if std.uni is even getting unittested right now. |
|
Okay looks like the testsuite has got the brilliant idea that it needs to run the generator.
But otherwise its looking like its passing :D |
The generator should sit outside of the std source tree, such as in a |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't see anywhere else that generated code would fall foul of the crude style checks.
|
Buildkite is failing due to a bug in mir-algorithm, so it's safe to assume as of right now, that this is green! |
It's only failing with this PR though, so perhaps you've indirectly affected something? |
Answer, yes: see Mir's implementation of So I'd consider you to be the owner of fixing Mir if you're going to break downstream. :-) |
Yeah it's calling into isGraphical, and the character in question wasn't allocated before 7 so it couldn't be graphical in previous tables. Should be an easy fix, remove one character from the unittest methodology effectively. |
5be3b7f to
6cddb97
Compare
6cddb97 to
8bd17c6
Compare
|
Looks like I'll have to remove myself as a code owner since I don't have write permissions |
14f643e to
4145185
Compare
|
cc @atilaneves . Any thoughts on this? |
|
I agree with @ibuclaw in that the generator should probably be in tools but it seems like it is already? |
It wasn't originally, but I applied that change since it made sense. The question is can we merge? I wanna get Turkic support into caseless matching ;) |
what the? I see in another PR has this exact issue for the same failed tests. So not my fault, phew. |
|
Rebasing to latest master will fix this. |
|
Oh dangit I shouldn't have let SourceTree merge branches like that. Oh well, I'll let CI run and confirm the fix for prior error. |
dacdd9d to
297370a
Compare
|
@atilaneves @ibuclaw any other objections or is this good to go? |
Right let's see how much this breaks.