You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that there are both cfg(miri) and cfg(not(miri)).
However, I found that PR #15284 has enabled cfg(miri) in analysis by default.
Currently my editor deactivates all the code blocks annotated with #[cfg(not(miri))], and I do not know how to activate those blocks or disable cfg(miri).
Is there any possible method in RA to activate code blocks with #[cfg(not(miri))]?
The text was updated successfully, but these errors were encountered:
@mccolljr I think currently there is no way to activate the lsp functionality on those blocks with #[cfg(not(miri))]. It is inconvenience for me at least.
internal: Cleanup cfg and env handling in project-model
Fixesrust-lang/rust-analyzer#16122 (comment)
`miri` and `debug_assertions` are now enabled via the `cargo.cfgs` config by default, allowing them to be disabled by overwriting the config.
I am reading codes of rust-vmm project, there is a code snippet like in the following:
Note that there are both
cfg(miri)
andcfg(not(miri))
.However, I found that PR #15284 has enabled
cfg(miri)
in analysis by default.Currently my editor deactivates all the code blocks annotated with
#[cfg(not(miri))]
, and I do not know how to activate those blocks or disablecfg(miri)
.Is there any possible method in RA to activate code blocks with
#[cfg(not(miri))]
?The text was updated successfully, but these errors were encountered: