Skip to content

Use our OOM-handling Vec in wasmtime_environ::Module#12584

Merged
fitzgen merged 1 commit intobytecodealliance:mainfrom
fitzgen:use-oom-handling-vec-in-environ-module
Feb 13, 2026
Merged

Use our OOM-handling Vec in wasmtime_environ::Module#12584
fitzgen merged 1 commit intobytecodealliance:mainfrom
fitzgen:use-oom-handling-vec-in-environ-module

Conversation

@fitzgen fitzgen requested review from a team as code owners February 12, 2026 21:18
@fitzgen fitzgen requested review from alexcrichton and removed request for a team February 12, 2026 21:18
Copy link
Member

@alexcrichton alexcrichton left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)

@github-actions github-actions bot added fuzzing Issues related to our fuzzing infrastructure wasmtime:api Related to the API of the `wasmtime` crate itself labels Feb 12, 2026
@github-actions
Copy link

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:

  • fitzgen: fuzzing

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

Learn more.

@fitzgen
Copy link
Member Author

fitzgen commented Feb 13, 2026

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

@fitzgen fitzgen force-pushed the use-oom-handling-vec-in-environ-module branch from 6cfb6c4 to 22273ff Compare February 13, 2026 21:19
@fitzgen fitzgen enabled auto-merge February 13, 2026 21:19
@fitzgen fitzgen added this pull request to the merge queue Feb 13, 2026
Merged via the queue into bytecodealliance:main with commit c782855 Feb 13, 2026
45 checks passed
@fitzgen fitzgen deleted the use-oom-handling-vec-in-environ-module branch February 13, 2026 21:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fuzzing Issues related to our fuzzing infrastructure wasmtime:api Related to the API of the `wasmtime` crate itself

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants