-
Notifications
You must be signed in to change notification settings - Fork 303
Remove highlighting for prelude types #3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
YES! This always bothered me. Personally though, I'd rather not have |
The current prelude items (excluding functions which are not treated specially) are these:
There are also When I first tidied up the list, it was a rather harum‐scarum list that had significant overlap with the prelude but both had and lacked certain items. Switching it to just the prelude was the easiest thing to do, and I think that it is still a good idea to have at least some of these things. If anyone like @blaenk wishes to remove the feature altogether, it’s not hard: hi link rustTrait NONE
" Option and Result:
hi link rustEnum NONE
" Some, None, Ok and Err:
hi link rustEnumVariant NONE The prelude was fairly diverse and bloated in the past; it has been tidied up a lot since this issue was filed in the Rust repository, though. There are now two categories of things in there as far as the traits are concerned: useful traits which you may wish to write, and extension traits to provide methods onto types (matching the form Also, incidentally, Overall my opinion is 👎 on removing the prelude items in part or in whole. I reckon that the |
Most of them are not even special cases in the compiler. E.g., giving Vec special highlighting makes no sense.
This looks like a reasonable subset:
The text was updated successfully, but these errors were encountered: