-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Javascript Target #18
Comments
Refs #18. This is still experimental, but we can now use sertop from the browser as a Worker. The jsCoq filesystem is not ported yet so you are limited to no prelude. Asynchronous support is also not available in this version.
Refs #18. This is still experimental, but we can now use sertop from the browser as a Worker. The jsCoq filesystem is not ported yet so you are limited to no prelude. Asynchronous support is also not available in this version.
Ok, basic support added, see a build is available at: https://github.com/ejgallego/jscoq-builds/tree/serapi an emulator is at: |
We optimize the size of the generated bytecode by not including Core_kernel. Still, the price we pay for Sexplib + serialization seems too high wrt to the standard jsCoq version (+ ~2MiB). Refs #18.
We optimize the size of the generated bytecode by not including Core_kernel. Still, the price we pay for Sexplib + serialization seems too high wrt to the standard jsCoq version (+ ~2MiB). Refs #18.
This indeed seems to save 1.8 MiB of bytecode! Refs #18.
Refs rocq-archive#18. This is still experimental, but we can now use sertop from the browser as a Worker. The jsCoq filesystem is not ported yet so you are limited to no prelude. Asynchronous support is also not available in this version.
We optimize the size of the generated bytecode by not including Core_kernel. Still, the price we pay for Sexplib + serialization seems too high wrt to the standard jsCoq version (+ ~2MiB). Refs rocq-archive#18.
This indeed seems to save 1.8 MiB of bytecode! Refs rocq-archive#18.
How much work would the JSON encoding be? That would be really nice to have. |
It should not be a lot of work and in fact I was looking forward to try it soon. I am not sure the Note that an easier approach would be to convert s-expressions to JSON in a systematic way using Javascript. This is the approach that Peacoq used and I think it worked pretty well. Encoding is fairly easy, a sexp |
Flèche issue ejgallego/coq-lsp#233 |
We want to compile SerApi to Javascript, Coq will run in a worker thread.
Thanks to jsCoq how to this is well understood. Once this is complete, jsCoq will just use SerAPI as its Coq implementation. For now, we will just communicate sending strings with the usual Sexp.
To do list is:
SerTop
Worker object.Core
is adding 1.8MiB so it is a large price to pay.The text was updated successfully, but these errors were encountered: