- From: William Casarin <jb55@jb55.com>
- Date: Sun, 16 Jul 2023 10:29:06 -0700
- To: Semisol <hi@semisol.dev>
- Cc: dev@damus.io, nostr-protocol@googlegroups.com, public-nostr@w3.org
On Sat, Jul 15, 2023 at 10:01:28PM +0300, Semisol wrote: > >> On 15 Jul 2023, at 21:10, William Casarin <jb55@jb55.com> wrote: >> >> On Mon, Jul 10, 2023 at 08:29:44PM +0300, Semisol wrote: >>>>> On 10 Jul 2023, at 18:24, William Casarin <jb55@jb55.com> wrote: >>>> >>>> On Mon, Jul 10, 2023 at 06:19:34PM +0300, Semisol wrote: >>>>> >>>>> … snipped … >>>>> My ABI exposes one import per command (I recommend you read it if you did not yet), which has some advantages, compared to a single interface: >>>>> >>>>> * You can know what a module can do beforehand, and modules that use >>>>> unsupported features will never be able to load, which helps >>>>> simplify development >>>>> * You still get to retain the typing on arguments >>>> >>>> Can you link or ideally mail it as a patch(set) for review? Then I would >>>> be able to respond inline here to comment on it. > >>> NOTE: Unsigned integers must be converted to signed while passing *to* wasm and >>> must be converted back to unsigned when received *from* wasm. >> >> why? > >Unsigned integers don’t exist in wasm when returning, so it has to be manually converted wow you would think writing a wasm interpreter from scratch in C I would remember this fact. probably because I support it transparently in one of my stack value enums... thanks xD
Received on Sunday, 16 July 2023 17:29:14 UTC