Fix the chrono format specification link - #4927
Merged
Merged
Conversation
vitaut
approved these changes
Sep 5, 2026
Contributor
|
Thanks for the fix. In the future, for simple cases like this I suggest skipping the issue and just opening the PR. |
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
2 participants
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.
Fixes #4926.
Point the chrono API reference to the existing explicit
chrono-format-specanchor in
syntax.md. The old plural fragment has no target.Validation:
1.18.0; the missing-anchor warning is gone.
api/index.htmllinks to../syntax/#chrono-format-spec, andgenerated
syntax/index.htmlcontains that ID. The old fragment is absent.git diff --checkpasses.One documentation line only; no API, syntax, dependency or CI change. On this
Windows host the build uses process-local UTF-8 mode; the separate default-codec
fix in #4925 is not included in this branch.