summaryrefslogtreecommitdiffstats
path: root/src/test/ui/span/issue-42234-unknown-receiver-type.rs
diff options
context:
space:
mode:
Diffstat (limited to 'src/test/ui/span/issue-42234-unknown-receiver-type.rs')
-rw-r--r--src/test/ui/span/issue-42234-unknown-receiver-type.rs19
1 files changed, 19 insertions, 0 deletions
diff --git a/src/test/ui/span/issue-42234-unknown-receiver-type.rs b/src/test/ui/span/issue-42234-unknown-receiver-type.rs
new file mode 100644
index 000000000..fd5312120
--- /dev/null
+++ b/src/test/ui/span/issue-42234-unknown-receiver-type.rs
@@ -0,0 +1,19 @@
+// revisions: full generic_arg
+#![cfg_attr(generic_arg, feature(generic_arg_infer))]
+
+// When the type of a method call's receiver is unknown, the span should point
+// to the receiver (and not the entire call, as was previously the case before
+// the fix of which this tests).
+
+fn shines_a_beacon_through_the_darkness() {
+ let x: Option<_> = None; //~ ERROR type annotations needed
+ x.unwrap().method_that_could_exist_on_some_type();
+}
+
+fn courier_to_des_moines_and_points_west(data: &[u32]) -> String {
+ data.iter()
+ .sum::<_>() //~ ERROR type annotations needed
+ .to_string()
+}
+
+fn main() {}