Conversation
Co-authored-by: xushiwei <396972+xushiwei@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Fix comments format bug for Clang and Python documentation
fix(cl): normalize C/C++ documentation comment markers
Oct 5, 2026
Member
|
@copilot The issue hasn't been resolved; CI on the Mac platform is still failing. |
Co-authored-by: xushiwei <396972+xushiwei@users.noreply.github.com>
Contributor
Author
The macOS failure came from enabling |
Co-authored-by: xushiwei <396972+xushiwei@users.noreply.github.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.
Comment extraction could leak decorative asterisks from block-comment delimiters into generated Go docs, and retain the
!marker from/*! ... */comments.The generated Go doc comment contains only
// Documentation text..