Signature xmldoc #14711
Merged
Signature xmldoc #14711
Conversation
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
…n xmldoc is missing.
auduchinok
approved these changes
Feb 7, 2023
vzarytovskii
approved these changes
Feb 7, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Display the signature xmldoc for an implementation symbol when implementation xmldoc is missing.
Use case:
When a function is backed by a signature, you will typically only write your
///comment in the signature file. Hovering over the usage of that function in any file will show you that comment. Unless you hover over that function in its implementation file.That is why I want to fall back to the XML comment of a signature when it is not present in the implementation file.