Specify wasm32-unknown-unknown target inside .cargo/config
#61
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
avrong
force-pushed
the
wasm-target-cargo-config
branch
from
18fdffa to
7c9d073
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The target setting in the cargo config can provide IDEs with an understanding of which target-specific code insight to show in the project. Both IntelliJ Rust and rust-analyzer respect this setting.
In IntelliJ Rust, the
wasm-pack-templateis one of the options to create a new project, and the inclusion of such a config setting seems to be convenient.Related to intellij-rust/intellij-rust#7262