Erik Rose
Erik Rose
The discussion on #9 shows we do need this.
Upstream patch is now merged.
> The proper result would be for backup to return exit code 3 I'm all in favor! :-) > I'm somewhat surprised that the resource forks are stored in extended...
@sunfishcode had a brilliant idea just now: what if we set aside RAM for the adapter not on the heap but by having a great big stack variable, over in...
Also got the skinny from Dan on why we can't easily use a second linear memory for the adapter state: Rust assumes memory 0, so you wouldn't be able to...
That did come up! I forget if it would be that straightforward or if there were cases where we still need to hit memory 0.
Having a swing at the [on-stack strategy](https://github.com/fastly/Viceroy/issues/498#issuecomment-3120452353) while you finish up what you're working on, Yan. If this works, it'll solve both TinyGo and Go.
To be super-duper clear (and to remind myself of this, because I just had a scary moment when I forgot it), if we get the stack and State out of...
Here are some of my "lab notes" thus far. Though this work has global applicability, I’ve been doing my development in Viceroy, in its Fastly-specific fork of the p1-to-p2 adapter,...
Further realization: if Go uses $__stack_pointer for any of its own stacks and we have Rust blithely do the same, Go and Rust frames will end up interlaced, and any...