wasmtime / PR #12479 fix: skip importing `std::path::Path... · git-wasmtime

Stream: git-wasmtime

Topic: wasmtime / PR #12479 fix: skip importing `std::path::Path...

Wasmtime GitHub notifications bot (Jan 30 2026 at 05:39):

HoKim98 requested fitzgen for a review on PR #12479.

Wasmtime GitHub notifications bot (Jan 30 2026 at 05:39):

HoKim98 requested wasmtime-core-reviewers for a review on PR #12479.

Wasmtime GitHub notifications bot (Jan 30 2026 at 05:39):

HoKim98 opened PR #12479 from ulagbulag:fix/skip-importing-path-regardless-of-cache-feature to bytecodealliance:main:

This PR just skips importing std::path::Path on crates/wasmtime/src/config.rs regardless of cache feature.

Currently, only either cranelift and winit feature requires importing it. cache feature is now unrelated.

The only use-case is here below:

https://github.com/bytecodealliance/wasmtime/blob/fdd8ed9e44f1df296568b1845c18d072b5e56681/crates/wasmtime/src/config.rs#L2706-L2711

Wasmtime GitHub notifications bot (Jan 30 2026 at 07:02):

github-actions[bot] added the label wasmtime:api on PR #12479.

Wasmtime GitHub notifications bot (Jan 30 2026 at 07:02):

github-actions[bot] added the label wasmtime:config on PR #12479.

Wasmtime GitHub notifications bot (Jan 30 2026 at 07:56):

github-actions[bot] commented on PR #12479:

Label Messager: wasmtime:config

It looks like you are changing Wasmtime's configuration options. Make sure to
complete this check list:

[ ] If you added a new Config method, you wrote extensive documentation for
it.

<details>

Our documentation should be of the following form:

```text
Short, simple summary sentence.

More details. These details can be multiple paragraphs. There should be
information about not just the method, but its parameters and results as
well.

Is this method fallible? If so, when can it return an error?

Can this method panic? If so, when does it panic?

Example

Optional example here.
```

</details>

[ ] If you added a new Config method, or modified an existing one, you
ensured that this configuration is exercised by the fuzz targets.

<details>

For example, if you expose a new strategy for allocating the next instance
slot inside the pooling allocator, you should ensure that at least one of our
fuzz targets exercises that new strategy.

Often, all that is required of you is to ensure that there is a knob for this
configuration option in [wasmtime_fuzzing::Config][fuzzing-config] (or one
of its nested structs).

Rarely, this may require authoring a new fuzz target to specifically test this
configuration. See [our docs on fuzzing][fuzzing-docs] for more details.

</details>

[ ] If you are enabling a configuration option by default, make sure that it
has been fuzzed for at least two weeks before turning it on by default.

[fuzzing-config]: https://github.com/bytecodealliance/wasmtime/blob/ca0e8d0a1d8cefc0496dba2f77a670571d8fdcab/crates/fuzzing/src/generators.rs#L182-L194
[fuzzing-docs]: https://docs.wasmtime.dev/contributing-fuzzing.html

<details>

To modify this label's message, edit the <code>.github/label-messager/wasmtime-config.md</code> file.

To add new label messages or remove existing label messages, edit the
<code>.github/label-messager.json</code> configuration file.

Learn more.

</details>