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

properly annotate C code in the guide #17239

Closed
wants to merge 1 commit into from

Conversation

steveklabnik
Copy link
Member

Without 'notrust,' we were getting a playpen link.

Fixes #17228.

Without 'notrust,' we were getting a playpen link.

Fixes rust-lang#17228.
@skade
Copy link
Contributor

skade commented Sep 15, 2014

Hm, shouldn't we use the logic as implemented in rustdoc? If it's not marked as rust or nothing at all, it should be ignored?

@huonw
Copy link
Member

huonw commented Sep 15, 2014

Theoretically that logic is there, I think writing this as ```c should work.

(i.e. remove the ignore, because that puts rustdoc into Rust mode: its thinking is: why would something be ignored unless it was Rust?)

@steveklabnik
Copy link
Member Author

I've made this change in the rollup PR, thanks.

@steveklabnik steveklabnik mentioned this pull request Sep 15, 2014
@steveklabnik steveklabnik deleted the for_loop branch October 25, 2017 18:26
lnicola pushed a commit to lnicola/rust that referenced this pull request May 19, 2024
internal: Key ignoring the job-id in metrics cache
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.

Guide: section on for loops shows C code which can be mistaken for Rust code
4 participants