Dov Murik

I don't have any permissions in this repo, and actually don't follow the development. There were comments (#497) about moving the development elsewhere but I haven't seen anything concrete.

LLVM has a wasm backend; so supposedly the .ll files generated by malc can be compiled to wasm instead of to x86_64 assembly. I haven't tried this. However, with wasm...

I'm sorry the server went down. I hope the messages are intact - `rabbitmq-dump-queue` never acks the messages, so they should stay in the queue if the client or server...

Maybe we can add some warning in the README of this possible outcome.

Add the RabbitMQ vhost name at the end of the AMQP URI. For example: rabbitmq-dump-queue -uri="amqp://user:[email protected]:5672/myvhost" ... Please let me know if worked — I'll add a short explanation about...

Thanks for the suggestion @gamesbook ! Unfortunately, I don't think RabbitMQ supports access to messages which are not at the head of the queue. Do you know about such option...

@gamesbook I'm not sure if it helps, but take a look at http://qdb.io/

Have you noticed this PR includes changes to make but also to ruby.2, vb, python.2? Is that intentional?

Sure.

See the [Pick a language](https://github.com/kanaka/mal/blob/master/process/guide.md#pick-a-language) section of the Mal implementation guide.