From 0ac5ed5a84799e52770cdd5edf0b8c099c3c0421 Mon Sep 17 00:00:00 2001
From: Aleksey Kladov <aleksey.kladov@gmail.com>
Date: Sat, 25 Apr 2020 21:11:18 +0200
Subject: [PATCH] Remove dead code

---
 editors/code/src/client.ts | 29 -----------------------------
 1 file changed, 29 deletions(-)

diff --git a/editors/code/src/client.ts b/editors/code/src/client.ts
index 0ad4b63aeb..f702829cdf 100644
--- a/editors/code/src/client.ts
+++ b/editors/code/src/client.ts
@@ -42,35 +42,6 @@ export async function createClient(serverPath: string, cwd: string): Promise<lc.
         clientOptions,
     );
 
-    // HACK: This is an awful way of filtering out the decorations notifications
-    // However, pending proper support, this is the most effecitve approach
-    // Proper support for this would entail a change to vscode-languageclient to allow not notifying on certain messages
-    // Or the ability to disable the serverside component of highlighting (but this means that to do tracing we need to disable hihlighting)
-    // This also requires considering our settings strategy, which is work which needs doing
-    // @ts-ignore The tracer is private to vscode-languageclient, but we need access to it to not log publishDecorations requests
-    res._tracer = {
-        log: (messageOrDataObject: string | unknown, data?: string) => {
-            if (typeof messageOrDataObject === 'string') {
-                if (
-                    messageOrDataObject.includes(
-                        'rust-analyzer/publishDecorations',
-                    ) ||
-                    messageOrDataObject.includes(
-                        'rust-analyzer/decorationsRequest',
-                    )
-                ) {
-                    // Don't log publish decorations requests
-                } else {
-                    // @ts-ignore This is just a utility function
-                    res.logTrace(messageOrDataObject, data);
-                }
-            } else {
-                // @ts-ignore
-                res.logObjectTrace(messageOrDataObject);
-            }
-        },
-    };
-
     // To turn on all proposed features use: res.registerProposedFeatures();
     // Here we want to enable CallHierarchyFeature and SemanticTokensFeature
     // since they are available on stable.