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

[fpos.operations] Unclear assertions in requirements table #1031

Closed
jlaire opened this issue Nov 14, 2016 · 3 comments
Closed

[fpos.operations] Unclear assertions in requirements table #1031

jlaire opened this issue Nov 14, 2016 · 3 comments

Comments

@jlaire
Copy link

jlaire commented Nov 14, 2016

The first row in "Table 108 — Position type requirements" contains expression P(i) in the first column and assertion p == P(i) in the last column. It is not clear what p refers to, since it is not used in the expression. Perhaps it is a typo and the assertion should be i == P(i).

The expression streamsize(o) has a corresponding assertion streamsize(O(sz)) == sz. The meaning of this is also unclear, since sz does not appear in the expression.

@jensmaurer
Copy link
Member

Regarding the first row: I have no clue what the editorial fix here should be. "p" is just any value of type P, so "p == P(i)" seems totally misguided. I'm asking for an LWG issue.

Regarding the conversions in the last row of the table: sz is introduced in the paragraph before the table: "sz refers to a value of type streamsize". So, these rows tell you that conversion from streamsize to streamoff, then back to streamsize is value-preserving for all possible values of type "streamsize".

@jensmaurer
Copy link
Member

@jensmaurer
Copy link
Member

See #2134 for the wholesale cleanup here.

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

No branches or pull requests

2 participants