Backticks within code blocks

[pittma]

👋 Hi all!

I have a chunk of rustdoc documentation which contains a compiler error that's causing rustfmt to return error code 101. I was able to isolate it down to backticks within the code block, the same behavior occurs with the following minimal example:

/// foo does things:
/// ```not_rust
/// Here's `foo` doing things
/// ```

Removing the backticks around foo in the example above results in a beautiful 0 return code.

If it's any help: I just returned to this project; its last commit was December 21 and I don't recall having issues then.

---

Here's my versions:

• Rustfmt: 0.3.8-nightly (346238f 2018-02-04)
• rustc: rustc 1.26.0-nightly (bedbad611 2018-02-26)
• My system:

  $ uname -a
  Linux dpitts-thinkpad 4.13.0-36-generic #40~16.04.1-Ubuntu SMP Fri Feb 16 23:25:58 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux
  

Cheers!

[pittma]

Two things:

1. This is also only happening with wrap_comments enabled.
2. I've traced this down into the parse call here, which has a panictry! in its path. I haven't yet isolated where in the parser the failure is occurring, but I did have a thought: During Rustfmt's pass through a code block annotated with anything other than rust, would it be a reasonable solution to not bookend that block with fn main() { and }, and just leave it untouched? Even if the user has wrap_comments enabled?