Andreas Rossberg

@Liedtke, it wouldn't require new opcodes, since the existing loads/stores already have an extension point with their flag field. We used that for multi-memories already. We would only need new...

@titzer, hm, I'm less sure about this option. That does not fit the (presumably common) use case well where there is more than a small, statically fixed number of array...

@titzer: > The idea with the bindable memories is that programs would use them to temporarily bind a slice to a memory index, do some operations on the temporary binding,...

@titzer: > I think rebinding is only brittle at the application level, not at the Wasm level. Hm, can you elaborate what you mean by that? I'd believe that using...

When I tried this locally before, I had to manually install a libffi package for Cygwin. Not sure why, I would think that ctypes-foreign includes it as a dependency. Unfortunately,...

Code 0xc0000135 is exactly what I got locally before installing libffi manually, after that it worked. I have no theory as for why, maybe it is a different libffi package...

So, I have a dumb question here: given that libffi versions like -6 and -8 are not fully ABI-compatible, where does the Opam package actually specify which version to depend...

Okay, I reproduced it by uninstalling the Opam packages `ctypes-foreign`, `conf-libffi`, and `conf-mingw-w64-x86_64-libffi`. I also uninstalled the Cygwin packages `mingw64-x86_64-libffi` and `mingw64-i686-libffi`. I then reinstalled `ctypes-foreign`. That also successfully reinstalled...

> I'm wondering whether that may play a part in the above, meaning that the Cygwin `libffi` packages are picked up instead of the MinGW ones. Maybe. Would that count...

What I can confirm is that it is looking for libffi-6.dll at runtime. I don't think libffi-8 matters. I also just noticed that the Cygwin [libff6 package](https://www.cygwin.com/cgi-bin2/package-cat.cgi?file=x86_64%2Flibffi6%2Flibffi6-3.2.1-2&grep=libffi) calls the actual...