doc(extension methods): typos and improvements, example with braces #9458
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
LPTK
reviewed
Jul 30, 2020
and remove note about type parameters for collective extensions. Since we have a unified syntax it should be clear that the same we explained for extension methods also apply to collective extensions as they are the same thing.
robstoll
force-pushed
the
doc-extension-methods
branch
from
472f822 to
3b8ae8d
Compare
nicolasstucki
approved these changes
Aug 4, 2020
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.
I removed the note about type parameters and using clauses from collective extension since we have a unified syntax now. I.e. it should be clear that the same we explained for extension methods also apply to collective extensions as they are the same thing.