[utilities] Consistently index all member typedefs in the utilites he… #6006
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.
…ader
Audited the file
utilities.tex
for indexing of member typedefs. Several idioms were in use, and not all typedef-names were indexed. Adopted what seemed to be the preferred approach of using the@\libmember{}@
style of definition within the class definition itself, so that omissions become obvious if more typedef-names are added in the future.Please provide feedback on whether indexing the explicit template specialization for types is the correct approach. It pulls out the name that is not present for the primary template, and then the ranges library adds some non-template classes with the same name.
Noted that
char_type
forbasic_format_arg
is a private member marked as exposition only, so should really bechar-type
with the expos-id font. After checking with the original paper, will supply a separate follow-up ticket for that --- this comment is only to confirm that the omission from the index in this patch is intentional.