SDK ext: Make Request/Response also be iostreams?
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
Research direction
The issue body names no files, tests, or entry points; begin by inspecting the SDK's Request and Response definitions and existing stream-related interfaces. Clarify the intended iostream behavior and scope before implementation, then add coverage showing the agreed usage works.
Written by the indexing model from the issue text.
Description
This issue has no description.
- Dominant language
- C++
- Stars
- 9
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Getting set up
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 88/100
tenstorrent/tt-metal#58057 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
maplibre/maplibre-native#4690 ·
Maintainers usually reply within 1 day
-
comp-query-execution
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
ClickHouse/ClickHouse#122569 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100