David Vázquez Púa

I think we can use github issues to keep track of what is missing. I created a ANSI Compliance milestone. Bugs and missing functionality from the standard can be assigned...

I am on holidays right now but I will write a small document with comments about the compiler and bootstrapping process next week. :)

it depends. If the functionality is big, led's say type system, it is probably pointless to create all tickets in advance. Instead a "Implement type system" is better. We can...

Just bad discipline from my side. I used to write comments for internal functions and do strings for public ones but I didn't stick to it.

I can try to examine your code to find the problem with `values`. But I don't like this approach too much. I see two other options that look more appealing:...

I'm not sure what we should do :-) I was just trying to give some ideas, but all options are open for now! Compatibility: https://caniuse.com/#feat=es6-class > which leads debuggers (Chrome,...

Cool. It's looking good. > (define-raw-builtin super (&rest args) > `(progn > (call |super| ,@(mapcar #'convert args)) > ,(bind-this))) How would you call the parent method of a class? Perhaps...

> (jscl:js-instanceof "String instance" #j:String) > => T that is probably never going to be true because strings in JSCL are implemented as arrays. The reason is that strings in...

Ok, I found the problem! Additionally I'll share a cool trick to debug this kind of problems. In the JSCL repl, evaluate `#:Object`. Then in the JS console, do `jscl.CL['*'].value`....

Note how that relates to the problem 3 from the FFI design discussions you just added: https://github.com/jscl-project/jscl/wiki/FFI-Design-Discussions#problem-3-conversion-between-lisp-and-js-values We definitely need that. Or even better, if we could think of a...