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

This comma confused me. Remove it #29099

Merged
merged 1 commit into from
Sep 9, 2018
Merged

This comma confused me. Remove it #29099

merged 1 commit into from
Sep 9, 2018

Conversation

pepsiman
Copy link
Contributor

@pepsiman pepsiman commented Sep 8, 2018

No description provided.

Copy link
Member

@Keno Keno left a comment

Choose a reason for hiding this comment

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

Thanks

@Keno Keno merged commit 68db9b4 into JuliaLang:master Sep 9, 2018
@fredrikekre fredrikekre added docs This change adds or pertains to documentation backport pending 1.0 labels Sep 9, 2018
@ViralBShah
Copy link
Member

I think it needs to be:

Values that cannot be stored in `UInt128` cannot be written as such literals.

This discussion is something I find useful on which vs. that.
https://www.chicagomanualofstyle.org/qanda/data/faq/topics/Whichvs.That.html

@ViralBShah
Copy link
Member

ViralBShah commented Sep 9, 2018

The sentence still sounds weird to me, especially the word such before literals.

@@ -178,7 +178,7 @@ of the binary data item is the minimal needed size, if the leading digit of the
`0`. In the case of leading zeros, the size is determined by the minimal needed size for a
literal, which has the same length but leading digit `1`. That allows the user to control
the size.
Values, which cannot be stored in `UInt128` cannot be written as such literals.
Values which cannot be stored in `UInt128` cannot be written as such literals.

Copy link
Contributor

Choose a reason for hiding this comment

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

I am not a native English speaker, but shouldn't a subclause that is essential (which is why the comma is not at its place), use "that" instead of "which", i.e. either of the following would be grammatically correct, but the latter does of course not have the correct meaning:

Values that cannot be stored in UInt128 cannot be written as such literals.

Values, which cannot be stored in UInt128, cannot be written as such literals.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Lose the double negative:
"Only values that can be stored in UInt128 can be written as such literals."

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs This change adds or pertains to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants