Repository navigation
Refine docs for RCSP - #668
andreacassioli wants to merge 1 commit into
Conversation
|
Boost dependency footprint vs Header-inclusion weights (graph files pulling each direct dependency in): No header-inclusion-weight changes. Transitive Boost modules: 47 → 47 (0) |
|
An automated preview of the documentation is available at https://668.graph.prtest3.cppalliance.org/libs/graph/doc/html/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-10-25 16:17:51 UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! 🚀 New features to boost your workflow:
|
|
Compiler-warning counts vs
|
| Before invocation, new_cont is initialized as a copy of old_cont. The function should mutate new_cont to reflect the resources consumed along the edge. | ||
|
|
||
| Return true if the extension is feasible, or false to discard the label (e.g. when a resource limit would be exceeded). The old_cont parameter is provided for reference, in case the update is more naturally expressed relative to the prior state. | ||
|
|
There was a problem hiding this comment.
some backticks got lost, "the function" is a bit vague compared to ref (it's already named), and some ideas are spread across the two paragraphs. Maybe something closer to:
Before `ref` is invoked, `new_cont` is initialized as a copy of `old_cont`. `ref` should update `new_cont` to reflect the resources consumed along `ed`. `old_cont` is passed for reference, in case the update is more naturally expressed relative to the prior state.
If `ref` returns `false`, the new label is discarded and the search does not extend along `ed` from that label.
There was a problem hiding this comment.
yeah I notice it looked not as I expected. I will check it out
Important
New algorithms and API additions need a design issue first. Such a PR is not reviewed until an issue has settled the API and frozen the scope. PRs whose scope grows under review go stale. See How To Contribute an Algorithm.
Motivation
The documentation is not clear about how some of the input parameters of the extension function are used.
Discussed in #351
What this PR does
Add a couple of lines to give more details to the user.
Before submitting
developbranch.Kind of change
Tick exactly one. Each kind is reviewed differently, so mixing them in one PR makes the diff difficult to review (why).
Change category