refactor!: remove push_to/pull_from and the source/sink concept family#368
Conversation
|
An automated preview of the documentation is available at https://368.capy.prtest3.cppalliance.org/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-07-23 16:12:00 UTC |
|
GCOVR code coverage report https://368.capy.prtest3.cppalliance.org/gcovr/index.html Build time: 2026-07-23 16:27:02 UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #368 +/- ##
===========================================
- Coverage 98.33% 98.07% -0.27%
===========================================
Files 152 132 -20
Lines 8288 6230 -2058
===========================================
- Hits 8150 6110 -2040
+ Misses 138 120 -18
Flags with carried forward coverage won't be shown. Click here to find out more.
... and 10 files with indirect coverage changes Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
d1f92f8 to
af619fc
Compare
The transfer algorithms push_to/pull_from and the source/sink concept family they rest on (ReadSource, BufferSource, BufferSink, WriteSink and the any_read_source/any_buffer_source/any_buffer_sink/any_write_sink wrappers) were consumed only by downstream libraries (http, beast2, burl) -- no capy algorithm uses them. Removed from capy: - concepts: read_source, buffer_source, buffer_sink, write_sink - io: push_to, pull_from, any_read_source, any_buffer_source, any_buffer_sink, any_write_sink - test mocks: buffer_source, buffer_sink, read_source, write_sink - 14 unit tests, 1 example (stream-pipeline); cuda/pipeline retained, rewritten to the any_*_stream wrappers - 11 Antora pages; nav, feature lists, and stream tutorials updated The stream concepts (ReadStream/WriteStream/Stream) and the any_*_stream wrappers stay -- they back capy's read/write algorithms and corosio's TLS. Four design essays (9c/9f/9i/9m) still reference the moved concepts in narrative and are left for an authorial pass. Resolves cppalliance#350 by removal rather than by an API change.
af619fc to
1c107c7
Compare
2 participants
The transfer algorithms push_to/pull_from and the source/sink concept family they rest on (ReadSource, BufferSource, BufferSink, WriteSink and the any_read_source/any_buffer_source/any_buffer_sink/any_write_sink wrappers) were consumed only by downstream libraries (http, beast2, burl) -- no capy algorithm uses them.
Removed from capy:
The stream concepts (ReadStream/WriteStream/Stream) and the any_*_stream wrappers stay -- they back capy's read/write algorithms and corosio's TLS.
Four design essays (9c/9f/9i/9m) still reference the moved concepts in narrative and are left for an authorial pass.
Resolves #350 by removal rather than by an API change.