Consider adding a config setting that exempts high frequency codepoints from minimum group sizes
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 13
- Forks
- 8
- Avg merge
- 3h 57m
- Merged PRs (30d)
- 7
Description
From @skef:
"One thing I was wondering was whether it might be worth plumbing through an exception to min_group_size for high frequency groupings, so that e.g. if there are only three codepoints that are high frequency in exactly {JP,SC} they don't get merged with others, the rationale being that high frequency codepoints don't have the same privacy implications."
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the existing min_group_size configuration and the grouping logic for high-frequency codepoints. Determine how an exception setting should interact with minimum group sizes, then add coverage for a high-frequency grouping smaller than the configured minimum; done means the behavior is configurable and tested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100