4 ms·
The exact shape is TBD (I target proc macros support for 0.3.0, whereas 0.2.0 will be about completeness/editors support), but in short -- I'm thinking about "p
by popzxc 1mo ago
The exact shape is TBD (I target proc macros support for 0.3.0, whereas 0.2.0 will be about completeness/editors support), but in short -- I'm thinking about "plugin"/DSL architecture where proc macro _effects_ can be described beforehand and applied by the LSP without actual code execution. Executing proc macros is a lot of effort, but LSP mostly cares about the externally observable effects, which is a much smaller subset.
- rdescartes 1mo agoIf it’s possible, that would be awesome. Do you mean that the author of the proc macro provides that information through attributes? (Disclosure: I originally implemented the proc-macro part of RA.)