chore: introducing fast-check feature #2205
Closed
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 current build scripts of the wasm(runtime) projects runs wasm builds unconditionally, which makes
cargo check
(which is called by rust-analyzer on save to perform compilation checks) extremely slow.I added a feature switch to disable these scripts when
cargo check
is called by rust-analyzer.This feature is never used on build, just for rust-analyzer only, with the following config:
.vscode/settings.json
: