about summary refs log tree commit diff
path: root/src/test/ui/reachable/expr_loop.stderr
diff options
context:
space:
mode:
authorVadim Petrochenkov <vadim.petrochenkov@gmail.com>2018-02-23 03:42:32 +0300
committerVadim Petrochenkov <vadim.petrochenkov@gmail.com>2018-02-26 20:24:02 +0300
commitfa2d9fc4b9e578d95fbf65613d1bf732fbdfb0d4 (patch)
tree1eb1a49b4750e2704d3d724fb4a12ea4e2237eff /src/test/ui/reachable/expr_loop.stderr
parentcdbd8c2f2aa69c4b8fe6f004449440e87c4ab87e (diff)
downloadrust-fa2d9fc4b9e578d95fbf65613d1bf732fbdfb0d4.tar.gz
rust-fa2d9fc4b9e578d95fbf65613d1bf732fbdfb0d4.zip
Update UI tests
Diffstat (limited to 'src/test/ui/reachable/expr_loop.stderr')
-rw-r--r--src/test/ui/reachable/expr_loop.stderr8
1 files changed, 4 insertions, 4 deletions
diff --git a/src/test/ui/reachable/expr_loop.stderr b/src/test/ui/reachable/expr_loop.stderr
index ce4b30c7984..7f834567de3 100644
--- a/src/test/ui/reachable/expr_loop.stderr
+++ b/src/test/ui/reachable/expr_loop.stderr
@@ -1,20 +1,20 @@
 error: unreachable statement
   --> $DIR/expr_loop.rs:19:5
    |
-19 |     println!("I am dead.");
+LL |     println!("I am dead.");
    |     ^^^^^^^^^^^^^^^^^^^^^^^
    |
 note: lint level defined here
   --> $DIR/expr_loop.rs:14:9
    |
-14 | #![deny(unreachable_code)]
+LL | #![deny(unreachable_code)]
    |         ^^^^^^^^^^^^^^^^
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
 
 error: unreachable statement
   --> $DIR/expr_loop.rs:31:5
    |
-31 |     println!("I am dead.");
+LL |     println!("I am dead.");
    |     ^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)
@@ -22,7 +22,7 @@ error: unreachable statement
 error: unreachable statement
   --> $DIR/expr_loop.rs:41:5
    |
-41 |     println!("I am dead.");
+LL |     println!("I am dead.");
    |     ^^^^^^^^^^^^^^^^^^^^^^^
    |
    = note: this error originates in a macro outside of the current crate (in Nightly builds, run with -Z external-macro-backtrace for more info)