bmerge could escape encoding checks if it is known to be ASCII

Open
#4,479 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Refactor
Clarity
Mostly clear
Activity status
Stale
Tech stack
r
Domain
data, performance

Research direction

Start by locating the bmerge implementation and reviewing the statistics from issue #4386. Investigate how character-field joins currently invoke ENC2UTF8 and how ASCII status could be established; done means reducing unnecessary encoding overhead without changing join behavior.

Written by the indexing model from the issue text.

Description

encoding internals joins

Having statistics from #4386 about any non-ASCII character we could escape ENC2UTF8 calls in bmerge and reduce overhead for joining on character fields.

Dominant language
R
Stars
3.9k
Forks
1.1k
Avg merge
14h 4m
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from Rdatatable/data.table

All issues in Rdatatable/data.table

Similar issues

More R issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.