Open Integralist opened 4 years ago
I'm having the same issue. Do we need to install syntastic?
@fifn2 @Integralist i to made the same observation, it was only after installing Syntastic that it started working, and seems as if only Syntatsic alone still won't give you error checking, they both need to be installed
Thanks @quadroli I'll give that a try tomorrow
Yeah, this plugin only includes a Syntastic checker; it doesn’t include Syntastic. We should probably try shifting that checker back over to Syntastic.
Syntastic’s kind of old school now, doing things in old and inferior ways. I wouldn’t recommend Syntastic to anyone any more.
ALE arose as a better alternative, better in many ways, and at least as good in almost all the rest. With the advent of Vim 8 and its improvements in asynchrony, it’s even more solid and superior.
Since then, its lunch has been mostly eaten by coc, which I switched to maybe a year ago.
So yeah, if you don’t have a particular reason to want to use Syntastic, I suggest giving coc plus coc-rust-analyzer a go. Not quite plug and play (make sure to read the coc documentation, there’s stuff you need to add to your vimrc to actually engage coc), but with slight effort, vastly superior to what you can get with Syntastic.
hmmm, @chris-morgan i to do notice significant slow downs when using syntastic with Rust, we talking nearly 2min worth of a wait between saves, gets quite frustating at times to, but i've stuck with it cause i feared swicthing to something like ALE or coc would require more memory and an internet connection, i truly dunno how they work but they both do seem to have server in their name so yeah, that's what kinda throws me off, could you kindly enlighten me
Edit: nvm, i think i got it, switched to ALE and now things are real smooth, no more lagging
I'm using vim-plug:
Steps to reproduce:
I was given a rust file that defined a
const
. I purposely deleted the const but left the reference to it in the code.Expected vs. actual behavior:
I expected the vim plugin to display an error, such as "your code references something that no longer is being defined" (I'm new to rust so I would have expected something like that from the rust compiler). But the actual behaviour was that nothing happened.
Debugging Info: