Repository navigation
docs: remove the seven passages three upstream fixes made false (Phase G) - #899
Merged
Merged
Conversation
Three upstream defects were documented here as known, cited issues — CTParser#338 (misleading Line n: prefix on parser errors), CTSolvers#216/#222 (GPU ExtensionError names the wrong missing package), and CTDirect#624 (:variable scheme advertised but not implemented). All three are now fixed upstream (CTParser 0.9.1-beta+, CTSolvers 0.5.5-beta+, CTDirect 1.1.2-beta+), and a fresh resolve confirms the reader gets a version carrying every fix. The seven passages describing these as live bugs now stated the opposite of what the code does, or documented a scheme that no longer exists. - choosing-a-method.md: drop the "with one exception" clause on the ExtensionError paragraph; delete the :variable scheme row and its "advertised but does not run" box (the scheme was removed upstream, not fixed); delete the Line 6: paragraph inside the :exa warning box (keeping its still-accurate prose and live @repl block); "two" -> "one" now that only the :exa box survives. - gpu.md / installation.md: rewrite the "it points the wrong way" paragraphs — the ExtensionError now correctly names CUDSS when that's the package actually missing. - docs/Project.toml + docs/src/assets/Project.toml: drop the self-referential OptimalControl deps entry. docs/make.jl loads this package via LOAD_PATH stacking (--project=. from the repo root), never through docs/Project.toml, and the entry had no matching [compat] line. Verified: docs build (julia --project=. docs/make.jl) is clean, unresolved @ref unchanged at 6, no other page references any of the four issue numbers. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Summary
Three upstream defects were documented on this site as known, cited issues:
Line n:prefix on parser errors#222 — the GPU
ExtensionErrornames the wrong missing package:variableadvertised but not implemented
All three are fixed upstream (CTParser ≥0.9.1-beta, CTSolvers ≥0.5.5-beta, CTDirect
≥1.1.2-beta), and a fresh resolve confirms this package's current
[compat]already picksversions carrying every fix. The seven passages describing these as live bugs now state the
opposite of what the code does, or document a scheme that no longer exists.
What changed
docs/src/solve/choosing-a-method.mdExtensionErrorparagraph (CTSolvers#222 fixedthe predicate — there's no exception left).
:variablescheme table row and the ":variableis advertised but does not run"box entirely — the scheme was removed upstream (CTDirect 1.1.2-beta), not fixed, so the
box's premise is false.
:exa" box, keeping itsstill-accurate prose and the live
@replblock.:exabox survives.docs/src/solve/gpu.md/docs/src/getting-started/installation.mdExtensionErrornow correctly namesCUDSSwhen that's the package actually missing.docs/Project.toml+docs/src/assets/Project.tomlOptimalControl[deps]entry (no matching[compat]lineexisted for it).
docs/make.jlloads this package viaLOAD_PATHstacking(
--project=.from the repo root — see the file's own header comment), never throughdocs/Project.toml.Verification
julia --project=. docs/make.jl: clean build, both before and after theProject.tomledit. Unresolved
@refcount unchanged at 6.grep -rn "CTParser#338\|CTSolvers#216\|CTSolvers#222\|CTDirect#624\|Line 6:" docs/src→no matches.
docs/src/tree beforehand for any other reference to these four issues,or any
@ref/anchor pointing into the deleted boxes — none found.docs/src/assets/Manifest.tomldeliberately left untouched: rebuilding picked up unrelateddependency-version drift (CTDirect, CTSolvers, CTParser betas that moved since this snapshot
was last generated) that doesn't belong in this PR.
No
[compat]change, no source change — pure documentation coherence, independent of thecompat-raise phase blocked on CTDirect#629.
🤖 Generated with Claude Code