Make public deserialize methods `deser_v2` & `deser_v2_compressed`
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 38/100
Research direction
Start by locating the public deserialize API and the deser_v2 and deser_v2_compressed methods in the Rust crate. Check how deserialize selects compressed versus uncompressed decoding, then make the requested methods directly callable and verify that uncompressed WASM use does not require compressed deserialization.
Written by the indexing model from the issue text.
Description
Specifically I'm interested in calling the deser_v2 method directly. My motivation is I'm using hdrhistogram in a WASM module where I only need to deserialize uncompressed histograms. By using the deserialize method the compiler can not statically determine that I will not be deserializing compressed histograms and flate2 gets included in my WASM.
I only included deser_v2_compressed in the title because I figured if you make public one of them then perhaps it makes sense to do both(??).
- Dominant language
- Rust
- Stars
- 373
- Forks
- 50
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 HdrHistogram/HdrHistogram_rust
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
HdrHistogram/HdrHistogram_rust#128 · 5 comments ·
-
Difficulty 3/5 1-2 days Newbie friendliness 32/100
HdrHistogram/HdrHistogram_rust#127 · 2 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
HdrHistogram/HdrHistogram_rust#120 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
HdrHistogram/HdrHistogram_rust#119 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 30/100
HdrHistogram/HdrHistogram_rust#114 · 3 comments · 1 reaction ·
All issues in HdrHistogram/HdrHistogram_rust
Similar issues
-
`categorize_command` has no `uv` arm, so every `rtk uv …` row counts as `other` in the ecosystem mixOpenarea:api bug good first issue priority:low
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
area/cli kind/bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
good first issue open-endedness: low type: new feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100