cfg_default! and its friends interfere with tooling #605
Comments
|
I know that work has been underway to fix this for quite some time in the IntelliJ Rust plugin. This thread discusses it more: intellij-rust/intellij-rust#1191. As a Clion user myself, I feel your pain, but I think this is a problem for the tool more than the libraries. |
spacekookie
added a commit
to spacekookie/async-std
that referenced
this issue
Jan 19, 2020
This was previously discussed in async-rs#605 and others as a source of high CPU load when sleeping tasks because of the overhead created by retrying a future in short succession.
spacekookie
added a commit
to spacekookie/async-std
that referenced
this issue
Jan 20, 2020
This was previously discussed in async-rs#605 and others as a source of high CPU load when sleeping tasks because of the overhead created by retrying a future in short succession.
ghost
pushed a commit
that referenced
this issue
Jan 20, 2020
This was previously discussed in #605 and others as a source of high CPU load when sleeping tasks because of the overhead created by retrying a future in short succession.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the Rust plugin in IntelliJ IDEA, the use of
cfg_default!,cfg_std!, and other similar macros prevents the IDE from discovering the top-level module declarations. That results in absolutely no IDE features working for the types and functions contained within those modules.async-std = "1.2.0"The text was updated successfully, but these errors were encountered: