Add FMT_UTF16 format flag
Open
Nobody has claimed this yet.
enhancement
non-trivial
- Dominant language
- C
- Stars
- 13.6k
- Forks
- 2.6k
- PR merge metrics
- No merged PRs in 30d
Description
This flag indicates that set_key() is to take a UTF32*UTF16* instead of a char* pointer to key. Formats like NT and Oracle will set it.
For eg. Incremental mode using UTF-32 internally, this means we don't have to go through (slow) UTF-8 conversion just to satisfy the legacy set_key() prototype.
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 locating the format flags and the set_key() entry point referenced in the issue, then trace how key pointers are currently handled. Done means FMT_UTF16 identifies UTF16* input for set_key() and avoids the unnecessary UTF-8 conversion described for incremental mode; verify the affected formats, including NT and Oracle.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100