From 93de13d93114b8850b0c745d47004fa904f310c5 Mon Sep 17 00:00:00 2001
From: Dmitriy Novozhilov <dmitriy.novozhilov@jetbrains.com>
Date: Fri, 1 Feb 2019 13:21:13 +0300
Subject: [PATCH] Fix behaviour of NI in testData

After one of previous commits (my or Mikhail Zarechenskiy) that test
  was broken and it's behaviour was not fixed. That test's behaviour
  is strange (why at one case we have `UNREACHABLE_CODE` and haven't
  at other) and needs further investigation
---
 .../nullableTypes/nullAssertOnTypeWithNullableUpperBound.kt     | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/compiler/testData/diagnostics/tests/nullableTypes/nullAssertOnTypeWithNullableUpperBound.kt b/compiler/testData/diagnostics/tests/nullableTypes/nullAssertOnTypeWithNullableUpperBound.kt
index 2393b321445..f43cfd17581 100644
--- a/compiler/testData/diagnostics/tests/nullableTypes/nullAssertOnTypeWithNullableUpperBound.kt
+++ b/compiler/testData/diagnostics/tests/nullableTypes/nullAssertOnTypeWithNullableUpperBound.kt
@@ -3,7 +3,7 @@ fun <T> test(t: T): T {
     if (t != null) {
         return t<!UNNECESSARY_NOT_NULL_ASSERTION!>!!<!>
     }
-    <!NI;UNREACHABLE_CODE!>return<!> <!ALWAYS_NULL!>t<!>!!
+    return <!ALWAYS_NULL!>t<!>!!
 }
 
 fun <T> T.testThis(): String {