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

Please see the contribution instructions for more information.

Error: Label const-hack can only be set by Rust team members

Please file an issue on GitHub at triagebot if there's a problem with this bot, or reach out on #t-infra on Zulip.

Hey! It looks like you've submitted a new PR for the library teams!

If this PR contains changes to any rust-lang/rust public library APIs then please comment with @rustbot label +T-libs-api -T-libs to tag it appropriately. If this PR contains changes to any unstable APIs please edit the PR description to add a link to the relevant API Change Proposal or create one if you haven't already. If you're unsure where your change falls no worries, just leave it as is and the reviewer will take a look and make a decision to forward on if necessary.

Examples of T-libs-api changes:

• Stabilizing library features
• Introducing insta-stable changes such as new implementations of existing stable traits on existing stable types
• Introducing new or changing existing unstable library APIs (excluding permanently unstable features / features without a tracking issue)
• Changing public documentation in ways that create new stability guarantees
• Changing observable runtime behavior of library APIs

@rustbot label +T-libs-api -T-libs

LGTM other than to make the types of constants &'static [T; N] instead of arrays to prevent copying.

Thank you for the helpful feedback and positive review, @fee1-dead.

I'm a new contributor, so I have a procedural question. Now that I've made the requested changes will you (or someone else) also have to tell bors r+ or will your GitHub approval be sufficient?

Looks good to me, thanks for the PR. An r+ is needed to merge. The GitHub approval is not used for this purpose.

@bors r+

Commit 2b328ea has been approved by fee1-dead

It is now in the queue for this repository.