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
{{ message }}
This repository has been archived by the owner on Nov 18, 2022. It is now read-only.
Our repo has multiple cargo workspaces. Each workspace has a different set of cargo features enabled. I don't know how to enable these features so that the VSCode editor correctly interprets the source code. For example, when we build in a particular workspace, we use the cargo command:
cargo build --features a,b
I don't know how to tell the IDE to enable features a and b. I have tried these settings:
Rust: All_features
Enable all Cargo features
and
Rust: Features (in settings.json)
"rust.features": [
"a",
"b"
]
Neither of these had any effect on the "squiggles" (errors) highlighted in the editor.
Is there a way to get the editor to correctly interpret the code based on the enabled features?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Our repo has multiple cargo workspaces. Each workspace has a different set of cargo features enabled. I don't know how to enable these features so that the VSCode editor correctly interprets the source code. For example, when we build in a particular workspace, we use the cargo command:
cargo build --features a,b
I don't know how to tell the IDE to enable features a and b. I have tried these settings:
Rust: All_features
Enable all Cargo features
and
Rust: Features (in settings.json)
"rust.features": [
"a",
"b"
]
Neither of these had any effect on the "squiggles" (errors) highlighted in the editor.
Is there a way to get the editor to correctly interpret the code based on the enabled features?
The text was updated successfully, but these errors were encountered: