Playgrounds rejects valid Rust (due to input processing?)

This code is expected to work but generates a compiler error due to a comment: https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=45b03c2e33ff3b6c20af40794c505c92

   Compiling playground v0.0.1 (/playground)
error: this file contains an un-closed delimiter
 --> src/main.rs:1:1854
  |
1 | pub fn main() {
    let reserved_names: [&str; 103] = [
        "as",
        "break",
        "const",
(snip)

If rust-playground tries to put all the code on a single line, that’s likely the problem. Thanks for building and maintaining such a useful tool; much appreciated!

[lqd]

Ha, this shows the content is not the whole problem, and unfortunately pasting it in/from github “fixes it”, as I think the issue is in the EOL delimiters. Here’s a repro for me of that last one, but constructed from the initial link.

I think the playground doesn’t see the mac \r in the code as end of lines.

[thedataking]

This fails with the same error and works for me locally:

pub fn main() {
    let r: [&str; 0] = [ // works locally; errors in playgrounds
    ];   
}