Viewing profile — chris6f

It's probably better to let the user/application decide what to do in these cases, and for this reason we allow them to register type-specific (de)serialization routines. In the ca…

It's a good point, but the entire program would have to be written this way (you can't use the standard library, or any other dependencies). What if there were tools to inspect and…

The library provides a way to serialize coroutine state, and to later deserialize that state and resume a coroutine from its last yield point. Where you store this state (in a DB, …

A source-to-source compiler, and a library that bundles runtime implementation details, was the path of least resistance. We'd love to integrate this with the Go compiler (`go buil…

We have a solution already, and we're exploring a few more. The durable coroutine library is one part of a larger system we're releasing soon. See https://stealthrocket.tech/blog/f…

Go v1.21, scheduled for release in August 2023, adds experimental support for the WebAssembly System Interface (WASI). It'll be possible to natively compile server-side WebAssembly…

Vector length agnostic programming has its own share of problems. I'm not familiar with the RISC-V V extension, but I assume it's similar to ARM's SVE. There's a good critical look…

We took a similar approach in our JSON decoder. We needed to support sets (JSON object keys) that aren't necessarily known until runtime, and strings that are up to 16 bytes in len…