Stream: git-wasmtime

Topic: wasmtime / issue #3670 Expose DefaultMemoryCreator in was...

Wasmtime GitHub notifications bot (Jan 10 2022 at 15:44):

alexcrichton commented on issue #3670:

FWIW the wasmtime-runtime crate is effectively a "private" crate which is not maintained from the perspective of having a pleasant-to-use API, instead it's existence is basically entirely for the wasmtime crate. In that sense while we could merge this now there's very little preventing a future refactoring from undoing this.

Is there any particular reason though why you're using wasmtime-runtime as opposed to wasmtime?

Wasmtime GitHub notifications bot (Jan 14 2022 at 13:42):

Mrmaxmeier commented on issue #3670:

Is there any particular reason though why you're using wasmtime-runtime as opposed to wasmtime?

I'm experimenting with Cranelift and a toy JIT. wasmtime-runtime's catch_traps and MmapMemory have been very useful for this :slightly_smiling_face:

FWIW the wasmtime-runtime crate is effectively a "private" crate which is not maintained from the perspective of having a pleasant-to-use API, instead it's existence is basically entirely for the wasmtime crate. In that sense while we could merge this now there's very little preventing a future refactoring from undoing this.

^ This would be fine for me – I'm currently just rebasing this patch every once in a while and wanted to clean up git dependencies :)

Wasmtime GitHub notifications bot (Jan 18 2022 at 15:17):

alexcrichton commented on issue #3670:

Ok, sounds reasonable to merge in that case!

Last updated: Nov 22 2024 at 16:03 UTC