Skip to content

Use code formatting for code-relevant values in std::fmt docs #28723

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

Merged
merged 1 commit into from
Sep 29, 2015
Merged

Use code formatting for code-relevant values in std::fmt docs #28723

merged 1 commit into from
Sep 29, 2015

Conversation

carols10cents
Copy link
Member

Especially when documenting the use of 0, since zero looks very
similar to O in fonts not meant for displaying code.

Other literal characters, traits, etc should also use code formatting.
This change makes this documentation more internally consistent.

Before this change, circled is the character I was using this documentation to find out about and that confused me when it wasn't immediately clear what character it was:

screen shot 2015-09-28 at 10 13 31 pm

After this change:

screen shot 2015-09-28 at 11 26 35 pm

I ran make check-docs and didn't break anything ⭐

Especially when documenting the use of `0`, since zero looks very
similar to `O` in fonts not meant for displaying code.

Other literal characters, traits, etc should also use code formatting.
This change makes this documentation more internally consistent.
@rust-highfive
Copy link
Contributor

r? @nikomatsakis

(rust_highfive has picked a reviewer for you, use r? to override)

@steveklabnik
Copy link
Member

👍 thanks!

@steveklabnik
Copy link
Member

@bors: r+ rollup

@bors
Copy link
Collaborator

bors commented Sep 29, 2015

📌 Commit a33d61a has been approved by steveklabnik

bors added a commit that referenced this pull request Sep 29, 2015
Especially when documenting the use of `0`, since zero looks very
similar to `O` in fonts not meant for displaying code.

Other literal characters, traits, etc should also use code formatting.
This change makes this documentation more internally consistent.

Before this change, circled is the character I was using this documentation to find out about and that confused me when it wasn't immediately clear what character it was:

<img width="1013" alt="screen shot 2015-09-28 at 10 13 31 pm" src="https://cloud.githubusercontent.com/assets/193874/10154708/c70815fe-6638-11e5-9acc-57c73a524203.png">

After this change:

<img width="981" alt="screen shot 2015-09-28 at 11 26 35 pm" src="https://cloud.githubusercontent.com/assets/193874/10154710/ce73eeb2-6638-11e5-98f7-902f58679316.png">

I ran `make check-docs` and didn't break anything ⭐
@bors
Copy link
Collaborator

bors commented Sep 29, 2015

⌛ Testing commit a33d61a with merge 9d009c0...

@bors bors merged commit a33d61a into rust-lang:master Sep 29, 2015
@carols10cents carols10cents deleted the 0-or-O-or-o branch September 29, 2015 17:55
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.

5 participants