fix: skip drop_fibers_and_futures when concurrency support is disabled by zacharywhitley · Pull Request #12515 · bytecodealliance/wasmtime
When the component-model-async feature is compiled in but the store was created without concurrency support (e.g., via Config tuning), concurrent_state is None. Calling concurrent_state_mut() in this case would panic due to the unwrap() on None. This fix adds a runtime check to early-return when concurrency_support is false, preventing the panic during Store drop.
This file contains hidden or 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