Joonsung Lee

Using luajit version greater than [2.1.0-beta3](https://www.freelists.org/post/luajit/LuaJIT210beta3) with GC64 option enabled solve the issue. Currently, `brew install luajit --devel --with-gc64` installs 2.1.0-beta3.

Not yet. As I know, there was some discussions about using QUIC as raw transport protocol on QUIC mailing list ( https://groups.google.com/a/chromium.org/forum/#!searchin/proto-quic/http/proto-quic/ZW15QLuLvoo/A35kdB20IAAJ ), though no one yet published well-formed working...

Your environment should be able to build https://github.com/devsisters/libquic , so you may have to install cmake, ninja or make, gcc and g++, and so on. Could you check it please?...

For local testing, you can generate a self-signed certificate/key pair and add to your OS's certificate store. Detail instructions are [here](http://www.chromium.org/quic/playing-with-quic). You can use chrome's --host-resolver-rules option, or /etc/hosts trick,...

Hi! - Which version of Chrome are you using? Old chrome (

To use libquic, some implementation-specific C++ classes should be implemented seperately, to fit on target language. Sample C++ implementations are here (net/tools/quic on chromium): https://chromium.googlesource.com/chromium/src.git/+/master/net/tools/quic/ Corresponding Go bindings are here:...