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

[lib] Harmonize references to standard library requirements. #1937

Closed
wants to merge 5 commits into from

Conversation

jensmaurer
Copy link
Member

Partially addresses #1263.

I haven't squashed the commits; I can do so if desired.

@jensmaurer jensmaurer assigned jensmaurer and unassigned jensmaurer Feb 20, 2018
@tkoeppe tkoeppe added the needs rebase The pull request needs a git rebase to resolve merge conflicts. label Mar 30, 2018
@jensmaurer jensmaurer removed the needs rebase The pull request needs a git rebase to resolve merge conflicts. label Mar 30, 2018
@jensmaurer
Copy link
Member Author

Rebased.

@tkoeppe
Copy link
Contributor

tkoeppe commented Mar 31, 2018

No need to squash, but could you move the [macros] change to the bottom so it comes first?

@jensmaurer
Copy link
Member Author

@tkoeppe: Done.

@@ -275,10 +275,10 @@
\pnum
\requires
\tcode{state_type}
shall satisfy the requirements of
shall satisfy the
\tcode{CopyAssignable} (\tref{copyassignable}),
Copy link
Contributor

Choose a reason for hiding this comment

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

This is one of the few cases where the placement of the reference is acceptable, since you are listing multiple requirements. In all cases where we only say one requirement, I would much prefer the reference after the word "requirements". Otherwise it's really disrutpive: "shall satisfy the Foo (Table n) requirements." vs "shall satisfy the Foo requirements (Table n)."

We even have a lot of precedent for that placement in the many other cases where we already say " shall satisfy the Foo requirements". So it wouldn't just read better, but also be more consistent.

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.

@@ -13031,7 +13031,7 @@
\indexlibrary{\idxcode{file_type}}%
\pnum
This enum class specifies constants used to identify file types,
with the meanings listed in Table~\ref{tab:fs.enum.file_type}.
with the meanings listed in Table~\tref{fs.enum.file_type}.
Copy link
Contributor

Choose a reason for hiding this comment

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

@jensmaurer: Extraneous "Table" here.

@@ -13074,7 +13074,7 @@
\pnum
The \tcode{enum class} type \tcode{copy_options}
is a bitmask type\iref{bitmask.types} that specifies bitmask constants used to control the semantics of
copy operations. The constants are specified in option groups with the meanings listed in Table~\ref{tab:fs.enum.copy_options}.
copy operations. The constants are specified in option groups with the meanings listed in Table~\tref{fs.enum.copy_options}.
Copy link
Contributor

Choose a reason for hiding this comment

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

Another extraneous "Table".

@@ -13074,7 +13074,7 @@
\pnum
The \tcode{enum class} type \tcode{copy_options}
is a bitmask type\iref{bitmask.types} that specifies bitmask constants used to control the semantics of
copy operations. The constants are specified in option groups with the meanings listed in Table~\ref{tab:fs.enum.copy_options}.
copy operations. The constants are specified in option groups with the meanings listed in Table~\tref{fs.enum.copy_options}.
Copy link
Contributor

Choose a reason for hiding this comment

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

And again.

@tkoeppe
Copy link
Contributor

tkoeppe commented Apr 1, 2018

General notes:

  • There are a few places left that say "meet(s) the requirements". I'm not sure if your plan as to remove all of those. If so, feel free to rebase those changes into the second commit.

  • A few of the "shall satisfy the Foo requirements" occurrences don't contain a cross reference. If you like, feel free to add one if it seems reasonable. (But we can leave that as is.)

@tkoeppe
Copy link
Contributor

tkoeppe commented Apr 2, 2018

Oh, I see that #1263 discusses the (lack of) cross references, so everything may already be as intended.

@tkoeppe
Copy link
Contributor

tkoeppe commented Apr 2, 2018

I fixed the duplicate "Table"s and pushed the results.

@tkoeppe tkoeppe closed this Apr 2, 2018
@jensmaurer jensmaurer deleted the b23 branch April 2, 2018 19:11
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

2 participants