Consider adding a config setting that exempts high frequency codepoints from minimum group sizes
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 42/100
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.
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."
- Dominant language
- C++
- Stars
- 13
- Forks
- 9
- Avg merge
- 14h 50m
- Merged PRs (30d)
- 6
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from w3c/ift-encoder
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
w3c/ift-encoder#271 ·
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
w3c/ift-encoder#262 ·
-
latest bazel does not workMay be free again @garretrieger claimed this 201 days ago, and no pull request is open. Open
w3c/ift-encoder#202 · 1 comment · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 38/100
w3c/ift-encoder#108 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
w3c/ift-encoder#105 · 4 comments ·
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
apache/rocketmq-clients#1469 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 9 days
-
自定义颜色添加为常用颜色Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
mg-chao/snow-apps#2227 · 2 comments ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
pnnx Python convert ignores fp16=False with input_shapesPossibly taken @ktz03 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Tencent/ncnn#7183 · 1 reaction ·
Maintainers usually reply within 1 day