-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
Machine readable rustc output #14863
Labels
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
Comments
Also, it would be good to have an option to check the syntax only, or even provide autocomplete proposals. |
steveklabnik
added
the
C-enhancement
Category: An issue proposing an enhancement or a PR with one.
label
Feb 14, 2015
Merged
bors
added a commit
to rust-lang-ci/rust
that referenced
this issue
Jun 5, 2023
fix: consider all tokens in macro expr when analyzing locals Fixes rust-lang#14687 2 fixes for `extract_function` assist (related closely enough that I squashed into one commit): - Locals in macro expressions have been analyzed only when they are in the top-level token tree the macro call wraps. We should consider all descendant tokens. - `self` in macro expressions haven't been analyzed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
I'm working on IDE integration (IntelliJ IDEA) for Rust, and it will be nice to have some kind of machine readable output when compiling with
rustc
, like thegdb/mi
interface does for debugging.Are there any plans to do something like this?
Maybe the best option will be integrating directly with
rustc
via JNI, although I'm not sure if this is actually feasible, or if will give me any better output.The text was updated successfully, but these errors were encountered: