Михаил Кормановский (Mikhail Kormanovskii)

Got the same bug, in v5.0.0. In v4.0.2 it works fine

It turns out that it is not a problem with yarn, because running `npm install` in similar environment fails with a similar error too and there are issues like this...

@kaby76 ok, I see. This is because I used the TypeScript version as a source and it contains class inherited from PythonLexer, not from Lexer. Will try the changes you...

@kaby76 I applied modifications you mentioned and was able to compile the code on my machine. Also, I fixed some typos which led to segfaults. Could you approve the workflow...

Got the same issue on 3.8.1. Solved by building the package from source: `conan install --build=mongo-*` @kmwagnera @sirasjad @ProNeverFake

A possible use case of this is to use Binaryen as a part of your own compiler targeting wasm. Wasm itself is being actively developed now and I think it...

> What is the benefit of the separation? The benefit is that you are able to compile many things into wasm modules (possibly in parallel), then link them together via...

In my opinion, this is better for logically distinguishing 3 different steps of the process and for (possibly) better parallelism. This allows using compiler-backend-only tool during (paralleled?) compilation without the...

In short, it is not compile time only, the file size/amount of files/compexity also matters. Let me provide more general use case which is similar to mine. 1. Wasm itself...

> a person might try using the smaller one This is a naming issue, I think. If the build is named with something like `no-optimizations` in it, I don’t expect...