Stream: git-wasmtime

Topic: wasmtime / PR #12216 Add support for map type

Wasmtime GitHub notifications bot (Dec 23 2025 at 21:42):

yordis opened PR #12216 from yordis:yordis/feat-map-support to bytecodealliance:main:

<!--
Please make sure you include the following information:

• If this work has been discussed elsewhere, please include a link to that
  conversation. If it was discussed in an issue, just mention "issue #...".

• Explain why this change is needed. If the details are in an issue already,
  this can be brief.

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

Wasmtime GitHub notifications bot (Dec 23 2025 at 21:43):

yordis edited PR #12216:

<!--
Please make sure you include the following information:

• If this work has been discussed elsewhere, please include a link to that
  conversation. If it was discussed in an issue, just mention "issue #...".

• Explain why this change is needed. If the details are in an issue already,
  this can be brief.

Our development process is documented in the Wasmtime book:
https://docs.wasmtime.dev/contributing-development-process.html

Please ensure all communication follows the code of conduct:
https://github.com/bytecodealliance/wasmtime/blob/main/CODE_OF_CONDUCT.md
-->

References

• https://github.com/bytecodealliance/wasm-tools/pull/2356
• https://github.com/WebAssembly/component-model/pull/554

Wasmtime GitHub notifications bot (Dec 23 2025 at 21:44):

yordis edited PR #12216:

Context

This is adding support for map based on https://github.com/WebAssembly/component-model/pull/554

References

• https://github.com/bytecodealliance/wasm-tools/pull/2356
• https://github.com/WebAssembly/component-model/pull/554

Wasmtime GitHub notifications bot (Dec 23 2025 at 21:51):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Dec 23 2025 at 21:52):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Dec 23 2025 at 21:53):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Dec 23 2025 at 23:46):

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

Subscribe to Label Action

cc @fitzgen

<details>
This issue or pull request has been labeled: "wasmtime:api", "wasmtime:c-api", "wasmtime:config", "wizer"

Thus the following users have been cc'd because of the following labels:

• fitzgen: wizer

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

Wasmtime GitHub notifications bot (Dec 24 2025 at 01:06):

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

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>

Wasmtime GitHub notifications bot (Jan 07 2026 at 18:09):

alexcrichton commented on PR #12216:

On a skim this looks like it's all in the right direction, thanks! As as a heads up the wasm-tools deps will be updated in https://github.com/bytecodealliance/wasmtime/pull/12254 which'll avoid the need for git deps. I'll take a closer look once this is further along in CI passing tests

Wasmtime GitHub notifications bot (Jan 07 2026 at 20:28):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 07 2026 at 20:32):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 07 2026 at 20:42):

yordis updated PR #12216.

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

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 07 2026 at 23:34):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 08 2026 at 10:17):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 08 2026 at 11:46):

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

Subscribe to Label Action

cc @fitzgen

<details>
This issue or pull request has been labeled: "fuzzing"

Thus the following users have been cc'd because of the following labels:

• fitzgen: fuzzing

To subscribe or unsubscribe from this label, edit the <code>.github/subscribe-to-label.json</code> configuration file.

Learn more.
</details>

Wasmtime GitHub notifications bot (Jan 08 2026 at 19:19):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 09 2026 at 02:46):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 16 2026 at 19:34):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 16 2026 at 19:55):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 16 2026 at 20:26):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 16 2026 at 20:28):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Jan 16 2026 at 20:28):

yordis created PR review comment:

Is it ok to do this? I kept getting things to commit locally, so I added this

Wasmtime GitHub notifications bot (Jan 16 2026 at 20:28):

yordis submitted PR review.

Wasmtime GitHub notifications bot (Jan 20 2026 at 20:18):

alexcrichton submitted PR review:

This is looking quite good to me, thanks for the thorough tests!

I haven't scrutinized the trampoline generation nor the lifting/lowering yet, but I can do that once the tests added here are passing (the #[ignore] ones at least).

If you can one thing I'd also recommend is modeling as many tests as possible as a *.wast test since that's generally the easiest to run and share (albeit difficult to write and debug)

Wasmtime GitHub notifications bot (Jan 20 2026 at 20:18):

alexcrichton created PR review comment:

Is this still applicable?

Wasmtime GitHub notifications bot (Jan 20 2026 at 20:18):

alexcrichton created PR review comment:

Yeah this is fine to have here, no worries

Wasmtime GitHub notifications bot (Jan 20 2026 at 20:18):

alexcrichton created PR review comment:

Mind splitting this out to a separate test file to avoid gating this preexsting test on the feature? It's not 100% relevant to us insofar as Wasmtime can put all the tests in one place, but in the interest of one day sharing tests with other runtimes it might be good to split things out by feature

Wasmtime GitHub notifications bot (Jan 20 2026 at 20:18):

alexcrichton created PR review comment:

Could this get scoped to just the tests in question using this feature?

Wasmtime GitHub notifications bot (Feb 06 2026 at 06:26):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 06 2026 at 06:42):

yordis submitted PR review.

Wasmtime GitHub notifications bot (Feb 06 2026 at 06:42):

yordis created PR review comment:

Yes, still applicable. Just that I learned I need to implement few traits still

Wasmtime GitHub notifications bot (Feb 06 2026 at 06:43):

yordis deleted PR review comment.

Wasmtime GitHub notifications bot (Feb 06 2026 at 07:15):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 06 2026 at 07:31):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 06 2026 at 08:47):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 06 2026 at 08:58):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 06 2026 at 09:43):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 06 2026 at 11:12):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 06 2026 at 11:45):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 06 2026 at 16:14):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 10 2026 at 20:12):

yordis requested alexcrichton for a review on PR #12216.

Wasmtime GitHub notifications bot (Feb 16 2026 at 23:06):

yordis updated PR #12216.

Wasmtime GitHub notifications bot (Feb 16 2026 at 23:07):

yordis has marked PR #12216 as ready for review.

Wasmtime GitHub notifications bot (Feb 16 2026 at 23:07):

yordis requested wasmtime-fuzz-reviewers for a review on PR #12216.

Wasmtime GitHub notifications bot (Feb 16 2026 at 23:07):

yordis requested wasmtime-core-reviewers for a review on PR #12216.

Wasmtime GitHub notifications bot (Feb 16 2026 at 23:07):

yordis requested wasmtime-default-reviewers for a review on PR #12216.

Wasmtime GitHub notifications bot (Feb 20 2026 at 21:16):

alexcrichton submitted PR review:

Mostly some thoughts about deduplication/sharing of the gnarliest bits below --

Wasmtime GitHub notifications bot (Feb 20 2026 at 21:16):

alexcrichton created PR review comment:

Shouldn't this take the alignment of the value into account too?

Another possibility would be to use CanonicalAbiInfo::record(...) to calcuate this since that'll help encapsulate the alignment/etc.

Wasmtime GitHub notifications bot (Feb 20 2026 at 21:16):

alexcrichton created PR review comment:

Is most of this code copied from translation lists? If so would it be possible to refactor things to share more amongst the two implementations?

Wasmtime GitHub notifications bot (Feb 20 2026 at 21:16):

alexcrichton created PR review comment:

Leftover TODO or still active?

Wasmtime GitHub notifications bot (Feb 20 2026 at 21:16):

alexcrichton created PR review comment:

This is a lot of duplication between HashMap and wasmtime_environ::collections::HashMap. Can this be refactored to avoid such duplication?

Wasmtime GitHub notifications bot (Feb 20 2026 at 21:16):

alexcrichton created PR review comment:

Clone here can be extremely inefficient, so can this be done without cloning all keys/values?

Last updated: Feb 24 2026 at 04:36 UTC