-
Notifications
You must be signed in to change notification settings - Fork 13.3k
unicode.py refactor part 1 #50922
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
unicode.py refactor part 1 #50922
Conversation
0633b35
to
33ebfa4
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
33ebfa4
to
ee35e1a
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
fd0b699
to
dc4902a
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
dc4902a
to
08a0f6c
Compare
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
08a0f6c
to
8eee38c
Compare
Picking someone from libs, r? @alexcrichton |
Sorry to only say this after you’ve done all this work, but what would you think of removing this Python code entirely and using https://github.com/BurntSushi/ucd-generate instead? Parts of the Python script have been copy-pasted at different points into a number of different crates, it would be nice to have instead a shared solution for the ecosystem. |
r? @SimonSapin |
@SimonSapin I agree that a fully-Rust version is ideal long term, although the main purpose of this is to make smaller changes that are easier to merge than a complete rewrite. I knew of |
In short, I don’t get the point of refactoring code if we have plans to entirely replace that same code. |
☔ The latest upstream changes (presumably #49283) made this pull request unmergeable. Please resolve the merge conflicts. |
Ping from triage @SimonSapin! What should we do with this PR then? Close it? |
I was hoping to discuss this some more with @clarcharr so that we find consensus, rather than closing unilaterally. @clarcharr should we hop on IRC at some point? |
I'd definitely be interested in talking more about this on IRC. I've been a bit busy this week and haven't had much time to get around to this. I'll open another PR after having some more discussion about this, but I'm not sure how long that'll be. I'll close this for now. |
I will follow this up with more changes in future PRs, although I figure that this work so far is enough to have an initial PR. The first commit here is just #50920, which is simple enough that it can be merged immediately; as such, this should be merged after #50920.
The goal of this is to simplify this file so that it's easier to understand and maintain. Moving the conversion logic into
mapping_table.rs
should make it easier to modify the case mapping tables for size and/or performance, which I also plan to do in a future PR.The contents of
tables.rs
don't actually change until the last commit.