Cargo Features
[dependencies]
fuel-vm = { version = "0.58.2", default-features = false, features = ["std", "alloc", "profile-coverage", "profile-any", "random", "da-compression", "serde", "test-helpers", "backtrace"] }
- default = std
-
The
std
feature is set by default wheneverfuel-vm
is added without
somewhere in the dependency tree.default-features = false - std default = alloc
-
Enables use_std of itertools ^0.10, std of fuel-asm, fuel-crypto, fuel-tx, and fuel-types
- alloc std test-helpers?
-
Enables fuel-tx, alloc of fuel-asm and fuel-crypto
- profile-gas profile-coverage = profile-any
- profile-any profile-coverage? profile-gas? = dyn-clone
-
All profiling features should depend on this
Affects
fuel-vm::profiler
… - random test-helpers? = rand
-
Enables random of fuel-crypto, fuel-tx, and fuel-types
- da-compression = fuel-compression
-
Enables da-compression of fuel-tx
- serde
-
Enables serde and serde_with and serde of fuel-asm, fuel-crypto, fuel-merkle, fuel-types, hashbrown ^0.14, and optional backtrace
backtrace:
requires debug symbols to work
- test-helpers = alloc, random, tai64
-
Enables anyhow, test-helpers of fuel-crypto and fuel-tx
Affects
checked_transaction::builder
,fuel-vm::memory_client
…
Features from optional dependencies
In crates that don't use the dep:
syntax, optional dependencies automatically become Cargo features. These features may have been created by mistake, and this functionality may be removed in the future.
- backtrace implicit feature
- dyn-clone profile-any?
- fuel-compression da-compression?
- rand random?
- tai64 test-helpers?