Closed huntc closed 3 years ago
bors r+
Hmm, this still doesn't make rust-analyzer work properly with the provided example file. It seems to think that the 51
, 52810
, 52811
, 52832
, 52833
, 52840
and 9160
features are all enabled at the same time.
Hmm, this still doesn't make rust-analyzer work properly with the provided example file. It seems to think that the
51
,52810
,52811
,52832
,52833
,52840
and9160
features are all enabled at the same time.
I shall investigate.
Hmm, this still doesn't make rust-analyzer work properly with the provided example file. It seems to think that the
51
,52810
,52811
,52832
,52833
,52840
and9160
features are all enabled at the same time.
If I take the Cargo.example.toml
as Cargo.toml
then open nvmc.rs
from common, I see this:
i.e. the correct highlighting was given that I'm just bringing in the 52840 feature. Do you see something similar?
If so then how are you observing that all features are enabled?
Ah, found the issue, I had rust-analyzer.cargo.allFeatures
enabled globally, will add that to our VS Code configuration.
This configuration update reflects the strategy taken with Embassy where a
Cargo.example.toml
is provided. This example is expected to be updated by the developer and customised for the target they are interested in. Without these changes, working withnrf-hal
is quite unpleasant in Visual Studio Code.A
Cargo.ci.toml
is provided and used by CI. This file is the originalCargo.toml
.Thanks to @Dirbaio for the recommendations.