Skip to content
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

[intro.defs] Remove cross-references to main part #4191

Merged
merged 1 commit into from Sep 14, 2020

Conversation

jensmaurer
Copy link
Member

@jensmaurer jensmaurer commented Sep 10, 2020

Partially addresses ISO/CS 016 (C++20 DIS)

Fixes cplusplus/nbballot#397

@jensmaurer jensmaurer added the ballot-comment Response to an NB or ISO comment on a ballot label Sep 10, 2020
@jensmaurer jensmaurer added this to the C++20 milestone Sep 10, 2020
@tkoeppe tkoeppe self-requested a review September 10, 2020 21:48
Copy link
Contributor

@tkoeppe tkoeppe left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe extend the commit message to say "cross-references from the Terms and Definitions to the main part".

Comment on lines -124 to -115
read\iref{conv.lval} or
modify (\ref{expr.ass}, \ref{expr.post.incr}, \ref{expr.pre.incr})
the value of an object
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we add some text to the note below to retain these useful xrefs? Perhaps add between the first and second sentence:

Reads of scalar objects are described in \ref{conv.lval} and modifications of scalar objects are describred in \ref{expr.ass}, \ref{expr.post.incr}, and \ref{expr.pre.incr}.

I think it's important to the use of this definition that we know what these four cases are.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

source/intro.tex Outdated
Comment on lines 346 to 347
templates that take two template arguments
and are declared in header \libheader{iosfwd}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we keep the two conditions the other way around? It makes more sense to me to start with all templates in <iosfwd> and then filter by "takes two arguments" than to start with the universe of all templates taking two arguments and then filter by "declared in <iosfwd>".

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fixed.

Definitions of terms cannot refer to subclauses in the main
body of the standard.

Partially addresses ISO/CS 016 (C++20 DIS)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ballot-comment Response to an NB or ISO comment on a ballot
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants