SDK ext: Come up with a better solution for converting Rust `Duration` to `std::chrono::duration`
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
Research direction
No files or tests are named. Start by locating the existing Rust Duration to std::chrono::duration conversion and inspect the public C++ interface to confirm what must remain unchanged. Done means the conversion no longer relies on a lossy 32-bit millisecond value without changing that public interface.
Written by the indexing model from the issue text.
Description
Currently, it's pretty lossy, using a 32-bit millisecond value. Shouldn't need to mess with the public C++ interface to fix this, though.
- Dominant language
- C++
- Stars
- 9
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
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.
More from fastly/compute-sdk-cpp
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fastly/compute-sdk-cpp#90 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
fastly/compute-sdk-cpp#87 ·
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
fastly/compute-sdk-cpp#88 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
fastly/compute-sdk-cpp#86 ·
-
documentation
Difficulty 4/5 3-5 days Newbie friendliness 30/100
fastly/compute-sdk-cpp#80 ·
All issues in fastly/compute-sdk-cpp
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
AXERA-TECH/ax-llm#77 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
games-on-whales/wolf#509 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
bug-unconfirmed
Difficulty 2/5 1-3 hours Newbie friendliness 76/100