We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Sometime we use build.rs to generate rust source, like bindgen, and then include the source by macro include.
build.rs
bindgen
include
For example:
include!(concat!(env!("OUT_DIR"), "/binding.rs"));
Imagine there is a function defined in binding.rs, and use in another mod, then operate the go to the definition.
binding.rs
go to the definition
Rust-analyzer will jump to the line include!(concat!(env!("OUT_DIR"), "/binding.rs"));,
Rust-analyzer
Clion with rust plugin will jump to real line in binding.rs.
Clion
I think is better to act like Clion, is more convenient.
The text was updated successfully, but these errors were encountered:
Duplicate of #3767
Sorry, something went wrong.
No branches or pull requests
Sometime we use
build.rs
to generate rust source, likebindgen
, and then include the source by macroinclude
.For example:
Imagine there is a function defined in
binding.rs
, and use in another mod, then operate thego to the definition
.Rust-analyzer
will jump to the lineinclude!(concat!(env!("OUT_DIR"), "/binding.rs"));
,Clion
with rust plugin will jump to real line inbinding.rs
.I think is better to act like
Clion
, is more convenient.The text was updated successfully, but these errors were encountered: