Fix Cargo.toml filtering

Add implementation note
Cleanup `is_relevant` usage

Author: alexheretic

src/actions/mod.rs

@@ -240,6 +240,8 @@ impl<'ctx> FileWatch<'ctx> {
     }
 
     /// Returns if a file change is relevant to the files we actually wanted to watch
+    // Implementation note: This is expected to be called a large number of times in a loop
+    // so should be fast / avoid allocation.
     #[inline]
     pub fn is_relevant(&self, change: &FileEvent) -> bool {
         let path = change.uri.as_str();
@@ -250,7 +252,7 @@ impl<'ctx> FileWatch<'ctx> {
 
         let local = &path[self.project_uri.len()..];
 
-        local == "/Cargo.lock" || local == "Cargo.toml"
+        local == "/Cargo.lock" || local == "/Cargo.toml"
             || local == "/target" && change.typ == FileChangeType::Deleted
     }
 }

src/actions/notifications.rs

@@ -277,13 +277,10 @@ impl<'a> NotificationAction<'a> for DidChangeWatchedFiles {
         let ctx = ctx.inited();
         let file_watch = FileWatch::new(&ctx);
 
-        // ignore irrelevant files from more spammy clients
-        if !params.changes.iter().any(|c| file_watch.is_relevant(c)) {
-            return Ok(());
+        if params.changes.iter().any(|c| file_watch.is_relevant(c)) {
+            ctx.build_current_project(BuildPriority::Cargo, out);
         }
 
-        ctx.build_current_project(BuildPriority::Cargo, out);
-
         Ok(())
     }
 }