From 218caa410aa38c29984be31a5229b9fa717560ee Mon Sep 17 00:00:00 2001
From: Daniel Baumann <daniel.baumann@progress-linux.org>
Date: Wed, 17 Apr 2024 14:19:13 +0200
Subject: Merging upstream version 1.68.2+dfsg1.

Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
---
 ...crlf-line-endings-string-literal-doc-comment.rs | 38 ++++++++++++++++++++++
 1 file changed, 38 insertions(+)
 create mode 100644 tests/ui/lexer/lexer-crlf-line-endings-string-literal-doc-comment.rs

(limited to 'tests/ui/lexer/lexer-crlf-line-endings-string-literal-doc-comment.rs')

diff --git a/tests/ui/lexer/lexer-crlf-line-endings-string-literal-doc-comment.rs b/tests/ui/lexer/lexer-crlf-line-endings-string-literal-doc-comment.rs
new file mode 100644
index 000000000..802be7f5a
--- /dev/null
+++ b/tests/ui/lexer/lexer-crlf-line-endings-string-literal-doc-comment.rs
@@ -0,0 +1,38 @@
+// run-pass
+// ignore-tidy-cr
+// ignore-tidy-cr (repeated again because of tidy bug)
+// license is ignored because tidy can't handle the CRLF here properly.
+
+// N.B., this file needs CRLF line endings. The .gitattributes file in
+// this directory should enforce it.
+
+// ignore-pretty issue #37195
+
+/// Doc comment that ends in CRLF
+pub fn foo() {}
+
+/** Block doc comment that
+ *  contains CRLF characters
+ */
+pub fn bar() {}
+
+fn main() {
+    let s = "string
+literal";
+    assert_eq!(s, "string\nliteral");
+
+    let s = "literal with \
+             escaped newline";
+    assert_eq!(s, "literal with escaped newline");
+
+    let s = r"string
+literal";
+    assert_eq!(s, "string\nliteral");
+    let s = br"byte string
+literal";
+    assert_eq!(s, "byte string\nliteral".as_bytes());
+
+    // validate that our source file has CRLF endings
+    let source = include_str!("lexer-crlf-line-endings-string-literal-doc-comment.rs");
+    assert!(source.contains("string\r\nliteral"));
+}
-- 
cgit v1.2.3