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
[support.dynamic] Improve cross-referencing for dynamic memory subcla… #3845
Conversation
…uses Update several cross-references to subclause 17.6 with more precise refernces to subclauses nested one level deeper. For the synopsis of the header, added a couple of banner comments with cross-references too. In addition, looked into ordering the global namespace declarations in front of opening namespace std to improve clarity, but that fails due to use of types declared in namespace std by this header!
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.
Banner comments usually have the same text as the reference's title.
Co-Authored-By: Johel Ernesto Guerrero Peña <johelegp@gmail.com>
Co-Authored-By: Johel Ernesto Guerrero Peña <johelegp@gmail.com>
Co-Authored-By: Johel Ernesto Guerrero Peña <johelegp@gmail.com>
I had managed to convince myself otherwise, but the counterexamples are few and far between, and mostly dropping a word or two, not rephrasing. Thanks for supplying the fixes too! |
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.
Please remove trailing whitespace:
support.tex:2008: // \ref{alloc.errors}, storage allocation errors <--- trailing whitespace
support.tex:2040:// \ref{new.delete}, storage allocation and deallocation <--- trailing whitespace
…uses
Update several cross-references to subclause 17.6 with more precise
refernces to subclauses nested one level deeper. For the synopsis
of the header, added a couple of banner comments with cross-references
too.
In addition, looked into ordering the global namespace declarations
in front of opening namespace std to improve clarity, but that fails
due to use of types declared in namespace std by this header!