Outdent example, preserving nested fence

[felixrabe]

No description provided.

[rust-highfive]

r? @frewsxcv

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

[felixrabe]

Still waiting for a local ./x.py doc to produce a result... First time actually running that script, I thought it would just build the docs :/

[felixrabe]

r? @steveklabnik

[felixrabe]

./x.py doc finished in ~45 min. Local build/x86_64-apple-darwin/doc/rustdoc/what-is-rustdoc.html looks fine.

[steveklabnik]

Can you show me a screenshot? I'm surprised this works, though maybe that's because this was written before we used pulldown-cmark, and it can handle it.

[felixrabe]

The CommonMark spec allows for nested fenced code blocks by requiring the same amount ({3,}) of opening and closing `'s or ~'s: https://spec.commonmark.org/0.29/#fenced-code-blocks.

So this is how the proposed change renders for me:

And this is the exactly same code (from ````text to ````), inlined in this comment:

# Docs
This is a project to test out `rustdoc`.
[Here is a link!](https://www.rust-lang.org)
## Subheading
```rust
fn foo() -> i32 {
1 + 1
}
```

[felixrabe]

Btw, to render ````text or ` in Markdown as I did above, use double backticks and a space around the code, e.g.:

`` ````text ``

and

`` ` ``

(Found by looking at https://spec.commonmark.org/0.29/changes.html#part-7.)

[Dylan-DPC-zz]

ping from triage @steveklabnik any updates?

[steveklabnik]

@bors: r+ rollup

sorry for taking so long here!

[bors]

📌 Commit 2823475 has been approved by steveklabnik