Hi, I am wondering if anyone has an idea of how to work around issue #1541. I am on macOS and hit it 100% of the time on my project. I confirmed using lldb as described in the issue. Is there perhaps a way to disable the language server features but still get error messages reported in vscode with cargo watch? Thanks :)
The issue link above isn't right, it's https://github.com/rust-analyzer/rust-analyzer/issues/1541
@David Yamnitsky to clarify, in lldb you see a thread stuck in
notify? Or in
chalk? We unfortunately have two different things that might cause 100% CPU
one sec, double checking...
It's in notify, not chalk
Thanks! Yeah, unfortunatelly there isn't a quick solution for this problem at the moment. I guess we should abstract away the file watching service and explore alternative backends, like watchman or vscode build-in watcher