summaryrefslogtreecommitdiffstats
path: root/tests/ui/macros/same-sequence-span.rs
diff options
context:
space:
mode:
authorDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-17 12:19:13 +0000
committerDaniel Baumann <daniel.baumann@progress-linux.org>2024-04-17 12:19:13 +0000
commit218caa410aa38c29984be31a5229b9fa717560ee (patch)
treec54bd55eeb6e4c508940a30e94c0032fbd45d677 /tests/ui/macros/same-sequence-span.rs
parentReleasing progress-linux version 1.67.1+dfsg1-1~progress7.99u1. (diff)
downloadrustc-218caa410aa38c29984be31a5229b9fa717560ee.tar.xz
rustc-218caa410aa38c29984be31a5229b9fa717560ee.zip
Merging upstream version 1.68.2+dfsg1.
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'tests/ui/macros/same-sequence-span.rs')
-rw-r--r--tests/ui/macros/same-sequence-span.rs22
1 files changed, 22 insertions, 0 deletions
diff --git a/tests/ui/macros/same-sequence-span.rs b/tests/ui/macros/same-sequence-span.rs
new file mode 100644
index 000000000..e0bb4d985
--- /dev/null
+++ b/tests/ui/macros/same-sequence-span.rs
@@ -0,0 +1,22 @@
+// aux-build:proc_macro_sequence.rs
+
+// Regression test for issue #62831: Check that multiple sequences with the same span in the
+// left-hand side of a macro definition behave as if they had unique spans, and in particular that
+// they don't crash the compiler.
+
+#![allow(unused_macros)]
+
+extern crate proc_macro_sequence;
+
+// When ignoring spans, this macro has the same macro definition as `generated_foo` in
+// `proc_macro_sequence.rs`.
+macro_rules! manual_foo {
+ (1 $x:expr $($y:tt,)* //~ERROR `$x:expr` may be followed by `$y:tt`
+ $(= $z:tt)* //~ERROR `$x:expr` may be followed by `=`
+ ) => {};
+}
+
+proc_macro_sequence::make_foo!(); //~ERROR `$x:expr` may be followed by `$y:tt`
+ //~^ERROR `$x:expr` may be followed by `=`
+
+fn main() {}