Handle std::string_view in top-level spreadsort

Open
#15 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
data

Research direction

Start with the top-level spreadsort overloads for std::string and std::wstring, then inspect how string_spread_sort handles character collections. Confirm what C++17 string_view types are available in the supported configurations. Done means the requested string_view overload support is covered and the vector and deque behavior is clarified.

Written by the indexing model from the issue text.

Description

The top-level spreadsort function has specific overloads targeting std::string and std::wstring specifically. With C++17 around the corner, these overloads could also accept std::string_view and std::wstring_view when they are available.

It notably helps std::string_view to be more of a "drop-in replacement for std::string" as much as possible.

By the way, is string_spread_sort also intended to sort collections of std::vector<char> or std::deque<char>, or is it not suited for these cases?

Dominant language
C++
Stars
58
Forks
47
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

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 boostorg/sort

All issues in boostorg/sort

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.