Add proc-macro related config and tests#3958
Conversation
|
Maybe it doesn't make sense, but could we put the functionality in the same binary to simplify deployment ( |
| macro_rules! t { | ||
| ($n:literal) => { | ||
| TokenTree::from(Ident::new($n, Span::call_site())) | ||
| }; | ||
| ({}) => { | ||
| TokenTree::from(Group::new(Delimiter::Brace, TokenStream::new())) | ||
| }; | ||
| (()) => { | ||
| TokenTree::from(Group::new(Delimiter::Parenthesis, TokenStream::new())) | ||
| }; | ||
| } |
There was a problem hiding this comment.
Writing proc-macro without syn and proc-macro2 crates is fun !!
Oh... sounds possible ? I like this idea and could simplify some code too. but I have to check whether it is possible in Windows. |
Yeah, I'd probably go with this way as well. Just let rust-analyzer spawn another rust-analyzer, and be careful not to create a fork-bomb accidentally :) |
edwin0cheng
force-pushed
the
add-install-script
branch
from
ebb1f67 to
28fd232
Compare
edwin0cheng
force-pushed
the
add-install-script
branch
from
28fd232 to
ca7dc69
Compare
|
Changed to use |
|
bors r+ |
|
Build succeeded: |
3 participants
This PR do the following things:
proc-macrofor running proc-macro server.To test it out:
"rust-analyzer.cargo.loadOutDirsFromCheck": true"and"rust-analyzer.procMacro.enabled": true"in vs code config.[Edit] Change to use
rust-analyzer proc-macrofor running proc-macro standalone process.