-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Use diagnostic item for Vec
#4519
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
Conversation
|
cc @oli-obk |
|
This fails because the item doesn't match. I probably should use the |
|
If there's no symbol in the sym list, you can call Symbol::intern("vec_type") At least I think there's a function called intern. As long as you don't use gensym, any way to create the symbol should be fine |
582fc66 to
0a78316
Compare
|
I left a few positions where either the paths were part of a slice of paths or the function would have needed a larger refactoring. |
|
Error seems unrelated. Do we need a rustup? |
0a78316 to
e3c4ffd
Compare
|
Rebased |
|
📌 Commit e3c4ffd has been approved by |
Use diagnostic item for `Vec` This adds a new `is_type_diagnostic_item` to check items without lookup via `match_type`. changelog: none
|
☀️ Test successful - checks-travis, status-appveyor |
|
Should we have a tracking issue of some sort for the different diagnostic items? |
This adds a new
is_type_diagnostic_itemto check items without lookup viamatch_type.changelog: none