summaryrefslogtreecommitdiffstats
path: root/src/test/ui/borrowck/two-phase-cannot-nest-mut-self-calls.rs
diff options
context:
space:
mode:
Diffstat (limited to 'src/test/ui/borrowck/two-phase-cannot-nest-mut-self-calls.rs')
-rw-r--r--src/test/ui/borrowck/two-phase-cannot-nest-mut-self-calls.rs19
1 files changed, 0 insertions, 19 deletions
diff --git a/src/test/ui/borrowck/two-phase-cannot-nest-mut-self-calls.rs b/src/test/ui/borrowck/two-phase-cannot-nest-mut-self-calls.rs
deleted file mode 100644
index dd2ef4e27..000000000
--- a/src/test/ui/borrowck/two-phase-cannot-nest-mut-self-calls.rs
+++ /dev/null
@@ -1,19 +0,0 @@
-// This is the third counter-example from Niko's blog post
-// smallcultfollowing.com/babysteps/blog/2017/03/01/nested-method-calls-via-two-phase-borrowing/
-//
-// It shows that not all nested method calls on `self` are magically
-// allowed by this change. In particular, a nested `&mut` borrow is
-// still disallowed.
-
-fn main() {
-
-
- let mut vec = vec![0, 1];
- vec.get({
-
- vec.push(2);
- //~^ ERROR cannot borrow `vec` as mutable because it is also borrowed as immutable
-
- 0
- });
-}