Randy Reddig
Randy Reddig
I think the current design moves some of the heavy lifting onto `wit-bindgen` and `wit-bindgen-go`, perhaps unnecessarily so. - Interface names are one example, and I did implement a somewhat...
Agreed the problems are orthogonal! Can name field be consistent with world key in all cases?
`wit-bindgen-go` uses the WIT package + world or interface name as extension to map to Go package paths, e.g.: - `wasi:cli/command` -> `wasi/cli/command` - `wasi:filesystem/types` -> `wasi/filesystem/types` For this WIT,...
I implemented a fix for this here: https://github.com/bytecodealliance/wasm-tools-go/pull/176 It nests named interfaces imported into or exported from a world under a Go package path for that world. This allows multiple...
Exported types referencing imported types should be interesting!
Would it make sense for each Interface, TypeDef, and Function to have a reference to its symmetric other (import vs export) if it exists?
@Mossaka you've probably realized or encountered this already: but I think this proposal means that every WorldItem would be duplicated at least once for each World in a Resolve.
This broke production for us, because `/` was pre-rendered with staging configuration. What’s the best way to disable pre-rendering of `/`, or any HTML?
I approve this licensing change.
I ran into a related issue with the wasmimport functions today and have a reproducer. Unfortunately the fix in this PR will not fix that issue, and instead result in...