Skip to content

Fix spelling, grammar, and stale identifiers in docs and Javadocs#222

Merged
sgerbino merged 1 commit intocppalliance:developfrom
sgerbino:pr/doc-i
Mar 9, 2026
Merged

Fix spelling, grammar, and stale identifiers in docs and Javadocs#222
sgerbino merged 1 commit intocppalliance:developfrom
sgerbino:pr/doc-i

Conversation

@sgerbino
Copy link
Collaborator

@sgerbino sgerbino commented Mar 9, 2026

  • doc/reference/concurrency-1.md: fix misspellings (exmaple_thread, initiazer), grammar errors, and remove duplicated content
  • doc 4c.executors.adoc: correct "two methods" to "three methods"
  • doc 8l.RunApi.adoc: fix garbled section symbol
  • doc why-capy.adoc: hyphenate "twenty-five", fix "with over decades"
  • task.hpp, thread_pool.hpp: fix stale repository URLs
  • io_awaitable.hpp, io_awaitable_promise_base.hpp: env->allocator and this_coro::allocator to env->frame_allocator and this_coro::frame_allocator
  • dynamic_buffer.hpp: string_buffers to string_dynamic_buffer with correct pointer syntax in code examples

Summary by CodeRabbit

  • Documentation
    • Refined semantic requirements and examples for resource allocation handling in asynchronous operations
    • Updated environment accessor conventions in coroutine documentation and examples
    • Clarified documentation terminology across concept definitions for consistency
    • Corrected official repository references in project headers

- doc/reference/concurrency-1.md: fix misspellings (exmaple_thread,
  initiazer), grammar errors, and remove duplicated content
- doc 4c.executors.adoc: correct "two methods" to "three methods"
- doc 8l.RunApi.adoc: fix garbled section symbol
- doc why-capy.adoc: hyphenate "twenty-five", fix "with over decades"
- task.hpp, thread_pool.hpp: fix stale repository URLs
- io_awaitable.hpp, io_awaitable_promise_base.hpp: env->allocator and
  this_coro::allocator to env->frame_allocator and
  this_coro::frame_allocator
- dynamic_buffer.hpp: string_buffers to string_dynamic_buffer with
  correct pointer syntax in code examples
@coderabbitai
Copy link

coderabbitai bot commented Mar 9, 2026

📝 Walkthrough

Walkthrough

This PR updates documentation and semantic requirements across concept and implementation headers, primarily renaming allocator references to frame_allocator in coroutine context and correcting repository URLs. No functional API changes.

Changes

Cohort / File(s) Summary
Repository URL Updates
include/boost/capy/ex/thread_pool.hpp, include/boost/capy/task.hpp
Updated official repository URLs from boostorg/capy and cppalliance/corosio to cppalliance/capy.
Frame Allocator Semantic Updates
include/boost/capy/concept/io_awaitable.hpp, include/boost/capy/ex/io_awaitable_promise_base.hpp
Renamed allocator references to frame_allocator in semantic requirements and environment-access documentation for consistency with coroutine context semantics.
Dynamic Buffer Naming Documentation
include/boost/capy/concept/dynamic_buffer.hpp
Updated documentation references from string_buffers to string_dynamic_buffer in adapter descriptions and conformance notes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • this and that #178: Directly related—both PRs modify allocator-to-frame_allocator migration in coroutine code paths (this_coro, io_env, await_transform, and related awaiters).
  • Audit javadocs #217: Related—both PRs touch overlapping headers (thread_pool.hpp, task.hpp) and update dynamic-buffer naming conventions.

Poem

🐰 Frame allocators hop with grace,
Through concepts in their proper place,
With URLs now fresh and bright,
The docs dance into the light!

🚥 Pre-merge checks | ✅ 2
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title addresses spelling, grammar, and documentation fixes, which aligns with most of the changes shown (URL updates, naming corrections, documentation updates), but undersells the semantic API change regarding allocator vs frame_allocator replacement.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
include/boost/capy/ex/io_awaitable_promise_base.hpp (1)

36-42: ⚠️ Potential issue | 🟡 Minor

Finish the terminology rename in the environment description.

Line 37 still says the stored io_env contains an allocator, but the public member is frame_allocator. Leaving the old term here makes this block inconsistent with the updated accessors and examples below.

✏️ Proposed fix
-    2. **Environment storage** — The mixin stores a pointer to the `io_env`
-       containing the executor, stop token, and allocator for this coroutine.
+    2. **Environment storage** — The mixin stores a pointer to the `io_env`
+       containing the executor, stop token, and frame allocator for this coroutine.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@include/boost/capy/ex/io_awaitable_promise_base.hpp` around lines 36 - 42,
Update the environment description to use the new terminology: replace the word
"allocator" with "frame_allocator" when describing the stored io_env so it
matches the public member names and the accessors; ensure the sentence that
currently reads "containing the executor, stop token, and allocator" instead
references "executor, stop token, and frame_allocator" and remains consistent
with this_coro::environment, this_coro::executor, this_coro::stop_token, and
this_coro::frame_allocator.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@include/boost/capy/ex/io_awaitable_promise_base.hpp`:
- Around line 36-42: Update the environment description to use the new
terminology: replace the word "allocator" with "frame_allocator" when describing
the stored io_env so it matches the public member names and the accessors;
ensure the sentence that currently reads "containing the executor, stop token,
and allocator" instead references "executor, stop token, and frame_allocator"
and remains consistent with this_coro::environment, this_coro::executor,
this_coro::stop_token, and this_coro::frame_allocator.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 45f9c964-5d7d-411a-af88-9fbdda261133

📥 Commits

Reviewing files that changed from the base of the PR and between 137bbd8 and 13ac669.

⛔ Files ignored due to path filters (4)
  • doc/modules/ROOT/pages/4.coroutines/4c.executors.adoc is excluded by !**/doc/**
  • doc/modules/ROOT/pages/8.design/8l.RunApi.adoc is excluded by !**/doc/**
  • doc/modules/ROOT/pages/why-capy.adoc is excluded by !**/doc/**
  • doc/reference/concurrency-1.md is excluded by !**/doc/**
📒 Files selected for processing (5)
  • include/boost/capy/concept/dynamic_buffer.hpp
  • include/boost/capy/concept/io_awaitable.hpp
  • include/boost/capy/ex/io_awaitable_promise_base.hpp
  • include/boost/capy/ex/thread_pool.hpp
  • include/boost/capy/task.hpp

@cppalliance-bot
Copy link

An automated preview of the documentation is available at https://222.capy.prtest3.cppalliance.org/index.html

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

2026-03-09 21:11:53 UTC

@cppalliance-bot
Copy link

GCOVR code coverage report https://222.capy.prtest3.cppalliance.org/gcovr/index.html
LCOV code coverage report https://222.capy.prtest3.cppalliance.org/genhtml/index.html
Coverage Diff Report https://222.capy.prtest3.cppalliance.org/diff-report/index.html

Build time: 2026-03-09 21:28:07 UTC

@sgerbino sgerbino merged commit 6957c0f into cppalliance:develop Mar 9, 2026
37 checks passed
@sgerbino sgerbino deleted the pr/doc-i branch March 9, 2026 21:40
@codecov
Copy link

codecov bot commented Mar 9, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.41%. Comparing base (8645de4) to head (13ac669).
⚠️ Report is 5 commits behind head on develop.

Additional details and impacted files

Impacted file tree graph

@@             Coverage Diff             @@
##           develop     #222      +/-   ##
===========================================
+ Coverage    92.14%   92.41%   +0.26%     
===========================================
  Files           77       81       +4     
  Lines         4534     4652     +118     
===========================================
+ Hits          4178     4299     +121     
+ Misses         356      353       -3     
Files with missing lines Coverage Δ
...nclude/boost/capy/ex/io_awaitable_promise_base.hpp 96.42% <ø> (ø)
include/boost/capy/ex/thread_pool.hpp 100.00% <ø> (ø)
include/boost/capy/task.hpp 96.15% <ø> (ø)

... and 10 files with indirect coverage changes


Continue to review full report in Codecov by Sentry.

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants