Repository navigation
doc: add a troubleshooting page - #133
Merged
Merged
Conversation
|
An automated preview of the documentation is available at https://133.openmethod.prtest3.cppalliance.org/libs/openmethod/doc/html/index.html If more commits are pushed to the pull request, the docs will rebuild at the same URL. 2026-10-18 16:53:48 UTC |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## develop #133 +/- ##
========================================
Coverage 92.34% 92.34%
========================================
Files 27 27
Lines 2234 2234
Branches 677 677
========================================
Hits 2063 2063
Misses 112 112
Partials 59 59
Continue to review full report in Codecov by Harness.
🚀 New features to boost your workflow:
|
Antora ignores any directory of a module that is not a family, so a page could not include the tested sources behind the reference's `include:` markers. Under examples/snippets/ they are reachable as `example$snippets/...`, and the troubleshooting page can show the same code as the reference instead of an untested copy. The `include:../examples/` markers become `include:../`, since the snippets now sit inside examples/. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Walks through the mistakes made most often - an overrider that matches no method, a call with a non-polymorphic class, missing class and base registrations, calls that cannot be dispatched - then indexes every diagnostic the library emits, at compile time and at run time, with its cause and remedy. The two compile errors shown on the page are tests: test/CMakeLists.txt and test/Jamfile also glob doc/modules/ROOT/examples/troubleshooting/compile_fail_*.cpp, so the messages the page quotes cannot drift from the library's. The runtime examples include the tested reference snippets. Salvaged from the fix/doc branch, whose captured compiler output had gone stale. Also drops a dead `:exampledir:` attribute from basics.adoc. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jll63
force-pushed
the
doc/troubleshooting
branch
from
October 18, 2026 16:46
062ec6f to
5045767
Compare
Closed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
(Written by Claude Code, on behalf of @jll63.)
#132 is merged, and this branch is rebased onto
develop, so the diff now shows only the two doc commits. The page documents the messages #132 added, and one of its examples checks one of them.Adds a Troubleshooting page (nav: after Shared Libraries, before Reference), salvaged and rewritten from the old
fix/docbranch. Its generated outputs were stale and it had factual errors.The page
static_assert.cannot find '...' method;const;final_virtual_ptrand its caveat.runtime_checksand which are always on (not implementedandambiguousare reported on every call), missing class registrations, missing bases, and calls that cannot be dispatched. Each example uses the already-testederrors_*snippets.static_assertand runtime message the library emits, grouped by area, each with its cause and remedy.Every compile-time example is a test. The page includes three
doc/modules/ROOT/examples/troubleshooting/compile_fail_*.cppfiles, each with anexpected-errormarker.test/CMakeLists.txtandtest/Jamfilenow glob that directory too, so a page example whose diagnostic changes fails the build. The MSVC wordings were captured with VS 18 BuildTools.Supporting changes
doc/modules/ROOT/snippets/moves todoc/modules/ROOT/examples/snippets/. Antora ignores module directories outside its families, so a page could not include the snippets. The//! include:markers in the headers anddoc/mrdocs.ymlfollow the move, and the reference pages still render them.basics.adoc: removes a dead:exampledir:attribute.CLAUDE.md: notes on the doc compile-fail glob and the snippets location.Verified
cpp:links resolve, noMRDOCSleaks.🤖 Generated with Claude Code
https://claude.ai/code/session_016NKQZ2ktRZ1AjCgSLLeXma