Paul Osborne

@brandonmoser Can you help get this merged? ideally we would like a set of active maintainers on this project with the commit bit. Alternatively we can work out where to...

I'm still remaining in hibernation on embedded-wg stuff for the time being as I get back to work, focusing on wasm stuff, but am hoping to continue to help with...

Personally, I tend to thing of `no_std` mostly in the context of projects without an OS (or at least a full-featured os like *nix), which would not be the case...

@fiveop Agreed. The executable size argument is valid (at least until LTO works more reliably or is enabled by default).

Pushed most of the updates but still need to make the suggested updates around the fat pointer stuff and resolve conflicts with upstream.

@fitzgen I believe this is ready for review again, let me know if there's pieces I missed in my previous updates. As noted, I chose to defer fatpointer changes for...

@fitzgen I am hunting down one regression with the latest, probably around the changes to table ops based on wasm types (though I haven't found a smoking gun yet). These...

Pulled in and resolved conflicts (some pretty mild ones from https://github.com/bytecodealliance/wasmtime/pull/11216. @fitzgen Review would be appreciated; I think in our last convos I had played around with a different fatpointer...

@fitzgen Yes, should be ready for review -- I'll just push a fixup for the CI issues. I sent a side note in zulip but I'll repost here: > Ok,...

@fitzgen I did run the test changes now -- a subset of those tests are now failing as it looks like there are some codepaths hit due to upstream changes...