I'm currently working on a project which relies heavily on types and functions generated within proc macros, and it can be a bit tedious to work with these due to lack of autocomplete. How feasible would it be to make autocomplete suggestions work in this case?
I would also be willing to investigate adding this, depending on complexity, if the project is looking for contributors.
It shouldn't, but sometimes it does. Namely, the proc macro ABI can change, and r-a needs to know how to call proc macros in order to expand them.
The toolchain now comes with a shim with a slightly more stable (IIRC, JSON-RPC-ish) interface that r-a knows how to use, but it's possible that your r-a isn't using it.
If you're using vscode, failure to expand proc macros is usually accompanied by an error popup. In other editors, I don't know how the error is (or isn't) reported.
I am using Zed and there is no error popup, but I can try in VSCode to see if there is some more feedback.
I know the proc macros are working at some level with RA, because I am using the diagnostics api to show localized errors within the proc macro invocations, and that is working perfectly.
Is there any way to test this independently of an editor? I.e. could I run RA from the terminal somehow and try to feed it an autocomplete request to see exactly what the output is?