Update Vim's Syntax highlinging

[mendess]

Update the official vim syntax highlighting. It's showing crate as an invalid keyword sometimes.

I tried opening a PR on there but they ask that the syntax's maintainer do it.

[pengshao]

+1 on this, i had to manually change it

[XVilka]

Would be nice to upstream it, indeed.

[blueyed]

According to vim/vim#5049 (comment) a new update should be sent to Bram for inclusion.

[chrisbra]

Note, there will be a new official Vim release pretty soon, so updating the runtime files now would be a good idea.

[tesuji]

+1 for this. What is blocking this from happening?

[tesuji]

cc @da-x

[adrian5]

The rust.vim that ships with (neo)vim was last edited 2017. Would be nice if we could offer users a more recent default, instead of expecting them to chase it down manually.

Btw, the current file still reads Last change: Feb 24, 2016. I would suggest to update that, because wrong information is worse than missing information.

[WhyNotHugo]

For those using neovim, I'd recommend looking at tree-sitter for handling highlighting. It's much lighter and done more efficiently.

There's also no incompatibility between it and this plugin, it'll just take over highlighting.

[XVilka]

While I perfectly understand the negative attitude towards JS, it's not a complete JS set, just a subset of it. Also, there was a proposal to remove the need for it, see the discussion at tree-sitter/tree-sitter#465
In general, it's much faster and more reliable than regex-based parsing and syntax highlight. Especially on more complex grammars of which Rust is a good example.