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

[over.best.ics] Turn a rationalizing footnote into a note with an acc… #1156

Closed
wants to merge 1 commit into from

Conversation

jensmaurer
Copy link
Member

…ompanying example.

Fixes #1152.

\tcode{f(B)}
is better than any of the sequences required to match
\tcode{f(A)}.}.
other user-defined conversion sequence. \begin{note}
Copy link
Contributor

@tkoeppe tkoeppe Nov 30, 2016

Choose a reason for hiding this comment

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

What do you think of making the note+example a new paragraph? (You could then even nest the example inside the note if you prefer.)

Copy link
Member Author

Choose a reason for hiding this comment

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

The note + example definitely belong to the "ambiguous conversion sequence" paragraph. The example highlights the entire preceding paragraph, not just the note, so nesting is not an option.

I could make the example (but not the note) a new paragraph. It seems we recently gravitate towards making long code examples separate paragraphs. Done.

class C { C(B&); };
B b;
int g(A);
int x = g(b); // error: selects g(A), but converting the argument is ambiguous (\ref{over.match.copy})
Copy link
Contributor

Choose a reason for hiding this comment

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

Should g(A) have some \tcode here?

Copy link
Member Author

Choose a reason for hiding this comment

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

Yes.

@jensmaurer
Copy link
Member Author

Mooted by #1232 and commit 81eea5e.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants