Alexey Knyazev

@kevmoo Have you had a chance to look into this?

My use case of reflection is docs generation via iterating over class members and invoking them to get sample outputs. The code using `dart:mirrors` resides in a `grinder` task thus...

As the author of [wasm_interop](https://pub.dev/packages/wasm_interop), I second that. The immediate issue is the difference between JS and Wasmer API designs.

Before making any suggestions, I'd list a few outstanding issues: - JS API strongly favors async compilation and instantiation. Some browsers refuse to compile large modules synchronously. - In JS...

@eseidelGoogle > I'm curious @lexaknyazev do you see these API design differences an insurmountable? Does this package need to end up as package:wasmer if so (e.g. would the API need...

> So the question is whether the JS API is so different that we will run into problems trying to squeeze it into the package:wasm interfaces. From our discussion so...

> Presumably the modules would all need to use the same store object? So I should add an assert that imported objects have the same store, right? Modules that use...

I simply run ``` > CompressonatorCLI.exe input.dds output.dds ```

FWIW, this command gives precise results: ``` > CompressonatorCLI.exe -UseGPUDecompress -DecodeWith DirectX input.dds output.dds ```

`CombinedIterableView` is slightly more performant (~6% using JIT) than `expand((e) => e)`. Also, `stream.expand` has a slightly different behavior than the snippet above: it adds all elements of the inner...