-
Notifications
You must be signed in to change notification settings - Fork 6
Fix Forwarding of Doc-Comments on Return-Parameters and Variant-Fields #818
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
InsertCreativityHere
merged 5 commits into
icerpc:main
from
InsertCreativityHere:fix-doc-comment-forwarding
Sep 4, 2026
Merged
Changes from 4 commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
3753e12
TEMP
InsertCreativityHere fad1f64
Fix handling of doc-comments on return-parameters and variant-fields.
InsertCreativityHere 8ec5be9
Review fixes.
InsertCreativityHere 6caebb6
Fix 'its'
InsertCreativityHere 55ad16f
Comment trimming work.
InsertCreativityHere File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is the same
Message-> overview conversion thatget_basic_doc_comment_from_messagedoes. The helper can't be used here as-is because it returns a wholeDocCommentand this impl needs the bare overview plus realsee_tags.Suggest extracting the message conversion itself, e.g.
fn convert_message(message: &slicec::grammar::Message) -> Message { message.value.iter().map(Into::into).collect() }, and calling it from bothget_basic_doc_comment_from_messageand here:There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not convinced this extra helper earns it's keep. It's a single-line of code, only called from 2 places.
I added it, and it actually increases our net-line-count by 3 lines.
I'd be fine with dropping your other helper (
get_basic_doc_comment_from_message) in place of theconvert_messagesuggestion. But if we added both helpers, then we'd have 2 helpers which are collectively only called by 3 places (that's together, not each). Only 1.5 calls per helper function is below the bar of usefulness IMO.If the implementations were longer, I could see the point, but both helpers are basically one-liners.