-
Notifications
You must be signed in to change notification settings - Fork 13.2k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Use const
s instead of static
s where appropriate
#22876
Conversation
(rust_highfive has picked a reviewer for you, use r? to override) |
☔ The latest upstream changes (presumably #22801) made this pull request unmergeable. Please resolve the merge conflicts. |
I would add a lint for |
☔ The latest upstream changes (presumably #22940) made this pull request unmergeable. Please resolve the merge conflicts. |
This looks good to me. I'd be happy to r+ a rebased version. |
This changes the type of some public constants/statics in libunicode. Notably some `&'static &'static [(char, char)]` have changed to `&'static [(char, char)]`. The regexp crate seems to be the sole user of these, yet this is technically a [breaking-change]
Rebased. r? @nikomatsakis |
☔ The latest upstream changes (presumably #22971) made this pull request unmergeable. Please resolve the merge conflicts. |
This changes the type of some public constants/statics in libunicode. Notably some `&'static &'static [(char, char)]` have changed to `&'static [(char, char)]`. The regexp crate seems to be the sole user of these, yet this is technically a [breaking-change]
This changes the type of some public constants/statics in libunicode.
Notably some
&'static &'static [(char, char)]
have changedto
&'static [(char, char)]
. The regexp crate seems to be thesole user of these, yet this is technically a [breaking-change]