-
-
Notifications
You must be signed in to change notification settings - Fork 40
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
Attribute macros support #789
Comments
|
I did and it says "[coc.nvim] Update completed", but I still see the same error/warning. |
I also did |
oh, this time I got an error on
On subsequent attempts, the update seems to succeed but then I'm back to my original problem. |
Looks like you're using an old coc.nvim, what's the output of |
You're correct. I upgraded successfully but seems now my nodejs is too old. :(
I guess I need to reinstall nodejs from another source as I'm already on the latest version available on my Ubuntu 20.04:
|
You can ignore the node warning, coc can work on nodejs 10. But it's recommended to use nodejs 12, nodejs 10 is already end of life. |
So I managed to upgrade everything I believe. However, I can't really test the new attribute macro feature as rust-analyzer-based completion in general isn't working for me any for some reason (it used to). :( Here is my configuration:
and here is what
btw, I now get error on another config:
|
This configuration has been renamed to another one. |
Readme needs to be updated then. :) No clue about why completion doesn't work for me anymore? |
@zeenix This configuration has been renamed in rust-lang/rust-analyzer#7868, README updated. Have no idea thy completion doesn't work for you. |
Probably rust-analyzer having issues with our codebase. 🤷 |
I actually tried different projects but it won't work. It's actually much worse, even renaming and highlighting won't work. :( To ensure the issue is not in coc, vim or my vim configuration, I tested against a C project using coc-clangd but all the features seem to work fine there, so it's either coc-rust-analyzer or rust-analyzer problem.
Could it be that rust-analyzer is too slow for coc and coc just ignores it's result/times out? |
|
What's the output of |
Thanks. Yes, seems there is a crash:
I guess now I can be confident about this being a rust-analyzer issue and report it there. :) Thanks so much! |
|
Recently attribute macros support was landed in rust-analyzer. However, I didn't see it working. Today I looked at the PR description and realized that I need to enable explicitly but when I enter the following line in my CoC config:
I'm told that it's not a valid property and it's also not listed in the properties in the README. Could you please add this configuration?
The text was updated successfully, but these errors were encountered: