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
Follow "semantic line breaks" in the LaTeX sources #2064
Comments
This one's even worse because we have a line break in the middle of a
This means to search for all occurrences of "trivially copyable types" you need to search in the generated PDF rather than the sources. This example also unnecessarily splits "arrays of such types" across two lines. |
I wouldn't be opposed to that being changed :-) |
We should decide whether "semantic line breaks" should become an editorial guideline. |
Editorial meeting consensus: This is already the convention; we simply need to document this policy. |
Added a sentence to the "Source code formatting" section of our "Specification Style Guidelines". |
Thanks! Should we close this now then? |
Since we're probably not doing fixes for violations unless we're editing in the vicinity, let's close this issue. |
See http://sembr.org/ and http://rhodesmill.org/brandon/2012/one-sentence-per-line/
The following example makes it hard to grep for "pointer types" in the source, because of an arbitrary line break that would have been better placed before "pointer":
Reformatting everything would be a huge amount of churn and make
git blame
less convenient, but it would be good to start following this style when making other editing changes.The text was updated successfully, but these errors were encountered: