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

Rustdoc: Highlight <code> elements (from Markdown backticks) #16296

Merged
merged 2 commits into from
Aug 6, 2014

Conversation

SimonSapin
Copy link
Contributor

No description provided.

@lilyball
Copy link
Contributor

lilyball commented Aug 6, 2014

What does this look like?

@SimonSapin
Copy link
Contributor Author

It’s very similar to what Github does: like this

@SimonSapin
Copy link
Contributor Author

This helps because the monospace font is not always enough to visually distinguish code from normal text.

@bors bors merged commit 3b41f32 into rust-lang:master Aug 6, 2014
@SimonSapin SimonSapin deleted the patch-8 branch September 20, 2014 19:25
lnicola pushed a commit to lnicola/rust that referenced this pull request Aug 13, 2024
feat: Implement TAIT and fix ATPIT a bit

Closes rust-lang#16296 (Commented on the issue)

In rust-lang#16852, I implemented ATPIT, but as I didn't discern ATPIT and other non-assoc TAIT, I guess that it has been working for some TAITs.

As the definining usage of TAIT requires it should be appear in the Def body's type(const blocks' type annotations or functions' signatures), this can be done in simlilar way with ATPIT

And this PR also corrects some defining-usage resolution for ATPIT
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.

4 participants