Stream: git-wasmtime

Topic: wasmtime / PR #12584 Use our OOM-handling `Vec` in `wasmt...

view this post on Zulip Wasmtime GitHub notifications bot (Feb 12 2026 at 21:18):

fitzgen opened PR #12584 from fitzgen:use-oom-handling-vec-in-environ-module to bytecodealliance:main:

Depends on

view this post on Zulip Wasmtime GitHub notifications bot (Feb 12 2026 at 21:18):

fitzgen requested alexcrichton for a review on PR #12584.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 12 2026 at 21:18):

fitzgen requested wasmtime-fuzz-reviewers for a review on PR #12584.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 12 2026 at 21:18):

fitzgen requested wasmtime-core-reviewers for a review on PR #12584.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 12 2026 at 21:46):

alexcrichton submitted PR review:

Related, but not blocking thought on this: collections::Vec is a bummer. Bikeshedding: if we were to rename wasmtime_environ::collections::Vec, what would we rename it to?

WDYT about maybe putting "t" or "T" in front of all the collections? For example tvec![...] and TVec and THashMap? (or any other letter really)

view this post on Zulip Wasmtime GitHub notifications bot (Feb 12 2026 at 22:52):

github-actions[bot] added the label fuzzing on PR #12584.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 12 2026 at 22:52):

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

view this post on Zulip Wasmtime GitHub notifications bot (Feb 12 2026 at 22:53):

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

Subscribe to Label Action

cc @fitzgen

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

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

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

Learn more.
</details>

view this post on Zulip Wasmtime GitHub notifications bot (Feb 13 2026 at 17:44):

fitzgen commented on PR #12584:

Related, but not blocking thought on this: collections::Vec is a bummer. Bikeshedding: if we were to rename wasmtime_environ::collections::Vec, what would we rename it to?

* `TryVec` - perhaps accurate, but long. `TryIndexMap` is a lot.

* `TVec` - personally I kinda like the ring of "letter plus collection". It's short and clearly "not `std`"

* `WVec` - wasmtime's vec?

* `XVec` - any other random letter

* `OomVec` - I don't like this b/c the container handles OOMs, it doesn't make OOMs

* `VecT` (or `VecW` or such) - subjectively not a fan

WDYT about maybe putting "t" or "T" in front of all the collections? For example tvec![...] and TVec and THashMap? (or any other letter really)

Yeah, I think something like this is inevitable if we aren't going to eventually move everything over to the OOM-handling versions.

I kind of hate all the potential names ~equally (no shade to you, they are basically the same candidates I've come up with myself).

I guess I like WVec the most maybe? Or if we are going to choose an arbitrary letter, might as well choose a cool one like XVec or something lol

view this post on Zulip Wasmtime GitHub notifications bot (Feb 13 2026 at 21:19):

fitzgen updated PR #12584.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 13 2026 at 21:19):

fitzgen has enabled auto merge for PR #12584.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 13 2026 at 21:32):

fitzgen added PR #12584 Use our OOM-handling Vec in wasmtime_environ::Module to the merge queue

view this post on Zulip Wasmtime GitHub notifications bot (Feb 13 2026 at 21:56):

fitzgen merged PR #12584.

view this post on Zulip Wasmtime GitHub notifications bot (Feb 13 2026 at 21:56):

fitzgen removed PR #12584 Use our OOM-handling Vec in wasmtime_environ::Module from the merge queue

Last updated: Feb 24 2026 at 04:36 UTC