From fad883e55ba4c6a02c8bb14053ddde6e0ba2c194 Mon Sep 17 00:00:00 2001
From: Nikolay Krasko <Nikolay.Krasko@jetbrains.com>
Date: Mon, 29 Jun 2015 18:59:27 +0300
Subject: [PATCH] Minor: remove outdated commit

---
 .../kotlin/storage/LockBasedLazyResolveStorageManager.kt        | 2 --
 1 file changed, 2 deletions(-)

diff --git a/compiler/frontend/src/org/jetbrains/kotlin/storage/LockBasedLazyResolveStorageManager.kt b/compiler/frontend/src/org/jetbrains/kotlin/storage/LockBasedLazyResolveStorageManager.kt
index e5017e6c5e9..07756c9020a 100644
--- a/compiler/frontend/src/org/jetbrains/kotlin/storage/LockBasedLazyResolveStorageManager.kt
+++ b/compiler/frontend/src/org/jetbrains/kotlin/storage/LockBasedLazyResolveStorageManager.kt
@@ -34,8 +34,6 @@ public class LockBasedLazyResolveStorageManager(private val storageManager: Stor
     override fun <K, V> createSoftlyRetainedMemoizedFunctionWithNullableValues(compute: Function1<K, V>) =
         storageManager.createMemoizedFunctionWithNullableValues<K, V>(compute, ContainerUtil.createConcurrentSoftValueMap<K, Any>())
 
-    // It seems safe to have a separate lock for traces:
-    // no other locks will be acquired inside the trace operations
     override fun createSafeTrace(originalTrace: BindingTrace) =
             LockProtectedTrace(storageManager, originalTrace)