Use core::string_view directly instead of alias

[ssam18]

This PR addresses issue #3046 by replacing all uses of the string_view alias with core::string_view throughout the codebase for improved clarity in both documentation and source code.

Changes

• Replaced string_view with core::string_view in all header files (.hpp)
• Replaced string_view with core::string_view in all inline implementation files (.ipp)
• Updated documentation files (.qbk) to use core::string_view
• Replaced basic_string_view with core::basic_string_view where applicable
• Retained type aliases in string_type.hpp for backward compatibility

Benefits

• Makes it explicit that Beast uses boost::core::string_view
• Improves code clarity and documentation
• Easier for users to understand the library's dependencies

Files Modified

• 48 header and implementation files
• 4 documentation files
• Total: 52 files with 410 insertions and 347 deletions

Closes #3046

[cppalliance-bot]

An automated preview of the documentation is available at https://3058.beast.prtest.cppalliance.org/libs/beast/doc/html/index.html

If more commits are pushed to the pull request, the docs will rebuild at the same URL.

2026-09-09 09:45:10 UTC

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.27%. Comparing base (66e232d) to head (3a47493).

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #3058      +/-   ##
===========================================
- Coverage    93.30%   93.27%   -0.03%     
===========================================
  Files          177      177              
  Lines        13764    13764              
===========================================
- Hits         12843    12839       -4     
- Misses         921      925       +4     

Files with missing lines	Coverage Δ
example/doc/http_examples.hpp	80.36% <100.00%> (ø)
...ude/boost/beast/_experimental/test/impl/stream.ipp	98.36% <ø> (ø)
include/boost/beast/_experimental/test/stream.hpp	75.00% <ø> (ø)
.../boost/beast/core/detail/impl/temporary_buffer.ipp	100.00% <ø> (ø)
include/boost/beast/core/detail/string.hpp	100.00% <100.00%> (ø)
...clude/boost/beast/core/detail/temporary_buffer.hpp	100.00% <ø> (ø)
include/boost/beast/core/impl/string.ipp	100.00% <ø> (ø)
include/boost/beast/core/string_type.hpp	100.00% <100.00%> (ø)
include/boost/beast/http/basic_parser.hpp	94.11% <ø> (ø)
include/boost/beast/http/chunk_encode.hpp	100.00% <ø> (ø)
... and 30 more

... and 1 file with indirect coverage changes

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 66e232d...3a47493. Read the comment docs.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ashtum]

Thank you. Could you please check the example and test directories as well?

[vinniefalco]

This is great!

[ssam18]

Thank you @ashtum for the review! I've updated the PR to:

1. Process example and test directories - added 58 more files with string_view replacements
2. Remove replace_string_view.py from the committed files

[ssam18]

Thank you for the detailed review! I've addressed all the feedback:

1. Removed the type aliases from string_type.hpp as they're no longer needed since all code now uses core::string_view directly
2. Removed the .gitignore entry for replace_string_view.py

[ssam18]

Fixed all remaining comment alignment issues.

[ashtum]

@ssam18 You can use the GitHub Action CI in your own fork to address the compile errors, since it won’t require approval to run each time.

[ssam18]

Why the core::string_view → boost::core::string_view change is necessary?

The issue:

C++ namespace lookup rules mean that when you write core::string_view in a file, the compiler searches for core starting from the current namespace and working outward. This works fine in files already inside namespace boost { ... } because the compiler finds boost::core. But in standalone example and test files that aren't wrapped in the boost namespace, the compiler can't find core at all.

FIX:

Files need to use the fully qualified name boost::core::string_view unless they're already inside the boost namespace. This is why:

Example files (like example/http/server/async/http_server_async.cpp) → Need boost::core::string_view (standalone programs)
Test/doc files outside boost namespace → Need boost::core::string_view
Header files inside namespace boost (like example/doc/http_examples.hpp) → Can use core::string_view (already in boost namespace)
This is standard C++ namespace behavior—you need the full qualification when you're not already in the parent namespace. The changes ensure MSVC (and all other compilers) can properly resolve the type regardless of where it's used.

[ssam18]

@ashtum Please let me know if this PR looks good?

[ashtum]

@ashtum Please let me know if this PR looks good?

All files under test/doc and example should use core::string_view rather than boost::string_view.
If needed, add namespace core = boost::core; in the correct location, following the style of nearby using declarations.

For example:

namespace beast = boost::beast;          // from <boost/beast.hpp>
namespace http = beast::http;            // from <boost/beast/http.hpp>
namespace websocket = beast::websocket;  // from <boost/beast/websocket.hpp>
namespace net = boost::asio;             // from <boost/asio.hpp>
namespace ssl = boost::asio::ssl;        // from <boost/asio/ssl.hpp>
namespace core = boost::core;            // from <boost/core/detail/string_view.hpp>
using tcp = boost::asio::ip::tcp;        // from <boost/asio/ip/tcp.hpp>

Please review each changed line manually and use your judgment to fix any formatting, clarity, or semantic issues.
Please run the CI on your branch and address the build failures (you need to activate GHA action for your fork).

[ssam18]

@vinniefalco vinniefalco after a long chase, I was able to fix all the failing tests after addressing the review comments. Please take a look at this PR.

[ssam18]

@ashtum please review this PR. This has been pending over months.

[ashtum]

@ssam18 Thanks for the effort here. After four rounds of reviews, there are still open issues (comment alignment in the doc snippets, redundant core namespace aliases inside boost::beast, and dangling string_view links in the docs), and a couple of earlier fixes have regressed. The review is now costing more than the change itself. I'll squash your commits and apply the required changes in a single commit.