Improve lowercased comments documentation #12579
Merged
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
Differentiate better between a full string character lowercased and a first character only lowercased
|
It might make sense to have the initial example string be a bit more plausible than "CAfé 🍵"; it looks like a typo. How about "BBQ Café 🍵", or some other word that naturally has capital letters after the first element? |
|
Thanks for this change, @Valpertui! |
|
@swift-ci Please smoke test |
natecook1000
approved these changes
Oct 24, 2017
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.
Improvement to the String.lowercased comments/documentation.
Differentiate better between a full string .lowercased and a first character only .lowercased