jscl
jscl copied to clipboard
A Lisp-to-JavaScript compiler bootstrapped from Common Lisp
Many built-in functions can be written on top of the FFI system. This would have also the benefit of making easier to interact with the Lisp runtime from JS.
As I commented in #189, it would be nice if travis-ci could also execute the tests in the host implementation via `jscl:run-tests-in-host`.
It would be good to have a benchs/ directory with some benchmarking. It is similar to tests/ but for measuring the performance. Nothing sophisticated, but I want to improve the...
It would be nice to have a simple website with links to the online REPL, instructions to get the project and so on. If you feel creative today, please give...
Builds are starting to take over a minute on my laptop, and one way to speed them up significantly would be to avoid recompiling files that haven't changed since the...
It is to say, the ability to generate human-readable Javascript code, instead of minified one. It is useful for debugging.
At the moment, printing a javascript object always results in `#`. It would be nice to have the fields printed: something like `#` for an object with an x property...
We could use ASDF defining custom components to distinguish host and target source files probably. The inconvenient of this is, of course, we could not get JSCL compiles itself completely,...
It looks that js source map support becomes a standard now. At least Chrome and Firefox have support for it. And source maps are really useful for debugging purposes. Several...
**We are considering changing the license of JSCL from GPL3 to MIT.** To do so, we need contributors of significant parts of JSCL to agree. If you are in this...