Use our OOM-handling Vec in wasmtime_environ::Module#12584
Use our OOM-handling Vec in wasmtime_environ::Module#12584fitzgen merged 1 commit intobytecodealliance:mainfrom
Vec in wasmtime_environ::Module#12584Conversation
alexcrichton
left a comment
There was a problem hiding this comment.
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.TryIndexMapis a lot.TVec- personally I kinda like the ring of "letter plus collection". It's short and clearly "notstd"WVec- wasmtime's vec?XVec- any other random letterOomVec- I don't like this b/c the container handles OOMs, it doesn't make OOMsVecT(orVecWor 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)
Subscribe to Label Actioncc @fitzgen DetailsThis 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 |
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 |
6cfb6c4 to
22273ff
Compare
Depends on
Stringusage inwasmtime_environ::Module#12565vec!macro for our OOM-handlingVec#12581Vecwith ranges #12582truncateandresizemethods to our OOM-handlingVec#12583