Is build file auto-reload a sensible default?

[susliko]

I've used rust-tools.nvim for some time and enjoyed that it picks any changes in Cargo.toml automatically.

I thought that this might make nvim-metals UX a little smoother. At the moment it raises a popup upon changes in build files.
Would it be practical at all considering a speed of re-import?

If yes, maybe some user survey could be done here?

[ckipp01]

So there were quite a few discussion about this on the main Metals repo, you could probably still find them. However, the idea was that if we would do an auto-import without any prompting it could lead to a really bad user experience since you'd probably be triggering way more imports (which can be really expensive) than needed. While there might be room to improve this, it's tricky. Either way the change would need to actually be made in upstream Metals, not here. I'll go ahead and transfer this discussion over there.

[tgodzik]

I wouldn't do that for sbt + Bloop. We can try that when using sbt via BSP, but we would need to make the experience there better.

[susliko]

Got it, thanks!