-
Notifications
You must be signed in to change notification settings - Fork 14.6k
[llvm] Proofread ProgrammersManual.rst #150787
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
base: main
Are you sure you want to change the base?
[llvm] Proofread ProgrammersManual.rst #150787
Conversation
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.
found some more missing ``. Not sure if all of those should be changed.
llvm/docs/ProgrammersManual.rst
Outdated
StringRef is ideal for passing simple strings around that are known to be live, | ||
either because they are C string literals, std::string, a C array, or a | ||
``StringRef`` is ideal for passing simple strings around that are known to be live, | ||
either because they are C string literals, ``std::string``, a C array, or a | ||
SmallVector. Each of these cases has an efficient implicit conversion to |
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.
SmallVector. Each of these cases has an efficient implicit conversion to | |
``SmallVector``. Each of these cases has an efficient implicit conversion to |
llvm/docs/ProgrammersManual.rst
Outdated
StringRef is ideal for passing simple strings around that are known to be live, | ||
either because they are C string literals, std::string, a C array, or a | ||
``StringRef`` is ideal for passing simple strings around that are known to be live, | ||
either because they are C string literals, ``std::string``, a C array, or a | ||
SmallVector. Each of these cases has an efficient implicit conversion to | ||
StringRef, which doesn't result in a dynamic strlen being executed. |
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.
StringRef, which doesn't result in a dynamic strlen being executed. | |
``StringRef``, which doesn't result in a dynamic ``strlen`` being executed. |
llvm/docs/ProgrammersManual.rst
Outdated
StringRef is ideal for passing simple strings around that are known to be live, | ||
either because they are C string literals, std::string, a C array, or a | ||
``StringRef`` is ideal for passing simple strings around that are known to be live, | ||
either because they are C string literals, ``std::string``, a C array, or a | ||
SmallVector. Each of these cases has an efficient implicit conversion to | ||
StringRef, which doesn't result in a dynamic strlen being executed. | ||
|
||
StringRef has a few major limitations which make more powerful string containers |
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.
StringRef has a few major limitations which make more powerful string containers | |
``StringRef`` has a few major limitations which make more powerful string containers |
This patch only adds double backticks around code-related terms to facilitate the review process.
ce79249
to
2fe5f39
Compare
@tgymnich Thanks for the review! I've incorporated your suggestions and fixed a few more. Please take a look. Thanks! |
``SmallVector``s would trigger an error.
This patch only adds double backticks around code-related terms to
facilitate the review process.