Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Functions that take a `std::string_view` but construct a `std::string` internally should just take a `std::string const&`

Open
#67 0 comments 1 reaction 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
Needs clarification
Activity status
Stale
Tech stack
cpp
Domain
api

Research direction

The issue names no files, tests, or entry points. Search the SDK for functions accepting std::string_view that construct std::string internally, then determine the complete set of affected call sites and bindings. Done means those signatures use std::string const& where appropriate and the relevant build or tests still pass.

Written by the indexing model from the issue text.

Description

technical improvement

This will avoid incurring additional allocations at the binding boundaries

Dominant language
C++
Stars
9
Forks
2
PR merge metrics
No merged PRs in 30d

Getting set up

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 fastly/compute-sdk-cpp

All issues in fastly/compute-sdk-cpp

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.