Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @nikomatsakis (or someone else) soon.

If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.

Please see the contribution instructions for more information.

@jonas-schievink, I ran the script to generate the file. I didn't mention that part because I thought it's obvious.

In #42998, I applied the change manually, because running the script also causes these changes. So, we can apply #42998 after this one, hopefully, to avoid breaking any instructions, theoretically.

CC'ing from file's blame/history: @petrochenkov, @cuviper, @alexcrichton, @SimonSapin

Oh, nevermind then, I thought you'd have to do some changes to the script itself.

Yeah, the script always fetches the latest version and there's no CLI option to change that. I think we should fix that, so we don't have to upgrade if we don't want to. (We don't keep the text data files in the repo.)

So, is there any reason to keep it as it is, or can I send a PR?

r? @alexcrichton -- I think this falls more into libs

@bors: r+

Thanks @behnam!

📌 Commit a6994d7 has been approved by alexcrichton

⌛ Testing commit a6994d7 with merge 734c836...

☀️ Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 734c836 to master...

Could you please check rust-lang/regex#391 as well. The regex crate would benefit from more recent Unicode compatibility as well.

See rust-lang/regex#400 for Unicode 10.0.

@cuviper Awesome!