e1d8ad3fb0
parser recovery (so that expected errors match up) I'm opting into parser recovery in all these cases out of expediency, not because the error messages you get with recovery enabled are actually all that usable in all cases listed.
33 lines
1.1 KiB
Rust
33 lines
1.1 KiB
Rust
// Copyright 2014 The Rust Project Developers. See the COPYRIGHT
|
|
// file at the top-level directory of this distribution and at
|
|
// http://rust-lang.org/COPYRIGHT.
|
|
//
|
|
// Licensed under the Apache License, Version 2.0 <LICENSE-APACHE or
|
|
// http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
|
|
// <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your
|
|
// option. This file may not be copied, modified, or distributed
|
|
// except according to those terms.
|
|
|
|
// compile-flags: -Z parse-only -Z continue-parse-after-error
|
|
|
|
// ignore-tidy-cr
|
|
|
|
/// doc comment with bare CR: '
|
|
'
|
|
pub fn foo() {}
|
|
//~^^ ERROR: bare CR not allowed in doc-comment
|
|
|
|
/** block doc comment with bare CR: '
|
|
' */
|
|
pub fn bar() {}
|
|
//~^^ ERROR: bare CR not allowed in block doc-comment
|
|
|
|
fn main() {
|
|
// the following string literal has a bare CR in it
|
|
let _s = "foo
|
|
bar"; //~ ERROR: bare CR not allowed in string
|
|
|
|
// the following string literal has a bare CR in it
|
|
let _s = r"bar
|
|
foo"; //~ ERROR: bare CR not allowed in raw string
|
|
|
|
// the following string literal has a bare CR in it
|
|
let _s = "foo\
|
|
bar"; //~ ERROR: unknown character escape: \r
|
|
}
|