Tracking issue for procedural macro support

Procedural macro support feature depends on the following ([experimental](https://plugins.jetbrains.com/plugin/8182-rust/docs/rust-faq.html#experimental-features)) features: - `org.rust.cargo.evaluate.build.scripts` - enables building and collecting build artifacts including proc-macro libraries during importing of project structure. **Enabled** by default - `org.rust.macros.proc.function-like` - enables expansion of [function-like](https://doc.rust-lang.org/reference/procedural-macros.html#function-like-procedural-macros) procedural macros. **Enabled** by default - `org.rust.macros.proc.derive` - enables expansion of [derive](https://doc.rust-lang.org/reference/procedural-macros.html#derive-macros) procedural macros. **Enabled** by default - `org.rust.macros.proc.attr` - enables expansion of [attribute](https://doc.rust-lang.org/reference/procedural-macros.html#attribute-macros) procedural macros To enable an experimental feature, type `Experimental feature` in the dialog of `Help | Find Action` action, enable the corresponding items and reload the project model via `Refresh Cargo Projects` action in Cargo tool window <img width="277" alt="image" src="https://user-images.githubusercontent.com/2539310/163798026-7d209eb2-a541-4c17-b8ca-061558709af8.png"> - [x] introduce proc macro server to evaluate procedural macro functions #6658 - [x] compile only "host" code of project: build scripts and proc-macro targets when `org.rust.cargo.evaluate.build.scripts` experimental fea

Posted by Undin on Mar 1, 2021, 8:50 AM

Tags

• support (Sysadmin)

Related issues

• Support connecting to remote devcontainers (devcontainer on remote host)
• Option to use Waffle menu or links displayed normally
• I also attempted to package ROCM on musl.
• But why is there no such pushback agains linux kernel?
• OpenCode Support
• Upcoming changes to the tado° API