chris6f | 2 years ago | on: Durable Coroutines for Go
chris6f's comments
chris6f | 2 years ago | on: Durable Coroutines for Go
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 debug the coroutine state? That's an area we're exploring now.
chris6f | 2 years ago | on: Durable Coroutines for Go
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, in a queue, etc) is up to you!
chris6f | 2 years ago | on: Durable Coroutines for Go
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 build -durable`, vs. `coroc && go build -tags durable`), but the compiler is closed and maintaining a fork of Go is not feasible for us at this time.
chris6f | 2 years ago | on: Durable Coroutines for Go
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/fairy-tales-of-workflow-orch... for more information :)
chris6f | 3 years ago | on: Transcoding Unicode with AVX-512: AMD Zen 4 vs. Intel Ice Lake
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 at SVE and VLA here: https://gist.github.com/zingaburga/805669eb891c820bd220418ee...
chris6f | 3 years ago | on: Quickly checking that a string belongs to a small set
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 length.
We got better performance with a linear scan and SIMD matching than with a hash table or a perfect hashing scheme.
See https://github.com/segmentio/asm/pull/57 (AMD64) and https://github.com/segmentio/asm/pull/65 (ARM64). Here's how it's used in the JSON decoder: https://github.com/segmentio/encoding/pull/101
page 1
In the case of network connections, the user could instead serialize connection details and then recreate the connection when deserializing the coroutine state. Same thing for files, where instead of serializing unstable low-level details like the file descriptor, the user can instead serialize higher level information (path, open flags, etc) and recreate the open file when deserializing the coroutine state.