Luke Wagner
Luke Wagner
A good observation in #276 is that the way we bind new `$identifiers` in component-level `export` definitions is a bit irregular, being the only place in WAT where we bind...
(Filing this for consideration later in a polish phase before 1.0; I don't expect this is a high priority until then since it's additive and I haven't heard anyone asking...
Reading configuration seems like a pretty common use case in the context of HTTP proxies. Now that wasi-runtime-config has made a bunch of progress, we should consider adding `import wasi:config/runtime`...
Once this proposal gets to Phase 3 and we can study the performance of realistic workloads, I think it's important for this group to measure a workload that, e.g., uses...
This PR builds on #363 to add `future` and `stream` type constructors along with the associated canon built-ins (`{stream,future}.new`, `{stream,future}.{read,write}`, `{stream,future}.cancel-{read,write}`). It also generalizes the "`async_subtasks`" table to also hold...
Currently, this `world` is valid: ```wit interface a { resource r; } interface b { use a.{r}; foo: func() -> r; } world w { import b; } ``` and...
This PR adds BuildTargets.md to define this new concept of "build targets" as presented in both [CG-06](https://docs.google.com/presentation/d/1Y-R2fsvsurfT1cpKMvxERnqAPvWlLgiEESiheUj-QUY/edit#slide=id.g2e1fc4d92ea_0_223) and [WASI-06-12](https://github.com/WebAssembly/meetings/blob/main/wasi/2024/WASI-06-13.md), which itself was a revision of the earlier "`wasit2`" idea that...
I think it would be beneficial to add a built-in `error` type to the Component Model and WIT to serve as the go-to type to use when you want to...
This isn't a fully-fleshed out idea, but it's coming up in #369 and so I thought it might be nice to split out here. I'm tentatively excited about it, though...