Skip to content

Conversation

hsivonen
Copy link
Member

Fixes #5796

@hsivonen hsivonen requested review from echeran and a team as code owners August 28, 2025 15:08
Copy link

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in issue comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

@hsivonen
Copy link
Member Author

I've spent way too much time trying to make the branches whose optimization brittleness I added comments about to do the right thing. It's not particularly worthwhile to put more effort into that before further changes to the normalizer, since pretty much anything can disturb how those compile, so it makes sense to do the other changes first.

@hsivonen hsivonen requested a review from Manishearth August 28, 2025 15:14
@hsivonen
Copy link
Member Author

I removed the new external dependency and instead imported cold_path and likely from rust-lang/hashbrown@64bd7db . See rust-lang/hashbrown@64bd7db#commitcomment-164768806 for permission to relicense those bits under Unicode-3.0.


/// Holder for either fast or small trie with the trie
/// type encoded into the Rust type.
pub enum Typed<F, S> {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: @sffc thoughts about the name? Typed isn't bad but there may be other ones that are better.

FastOrSmall?

Copy link
Member

@Manishearth Manishearth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LG with one nit

@@ -65,13 +65,13 @@ utf8_iter = ["dep:utf8_iter"]
# behind `not(serde)` instead. See a comment in `lib.rs` for
# the TODO list explaining why the relevant bits aren't
# already behind `not(serde)` instead.
# unstable_fast_trie_only = []
# icu4x_unstable_fast_trie_only = []
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: we're not using this feature anymore, just the cfg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Small-only and Fast-only getters for CodePointTrie
3 participants