David Vázquez Púa

> BTW, is there a list of non-implemented features? (Aside from the README.) Not really, we used to have a file with all symbols from CLHS and their implementation status,...

Very interesting. Compare ```lisp (progn (read-from-string "1d999") nil) ;; works (progn 1d999 nil) ; hangs! ``` First one suggests that is not the reader. But `(read-from-string "1d999")` fails.. so maybe...

But if it is reader, how the first example `(progn (read-from-string "1d999") nil) ` works? Or even `(integerp (read-from-string "1d999"))`. Or at least they don't hang.

Sure, but setting aside the fact that we could signal an error. I would expect the code still to just give a meaningless result, but never to hang. But I...

It should be easy. It is just a `setf` on the `car` or `cdr` of a `c[d]*r`. But we are missing the easy ways to define setf expanders. Right now...

I think it is a perfect question, I am not sure but it doesn't seem to be possible yet. So it is a good opportunity to implement it. My proposal...

You are right. I don't know what I was thinking. It works :). My concern was that `(new (f X))` didn't seem a good syntax. It would still need new...

Anyway, I think that ``` lisp (new #'f x) ``` will work. It allow us to easily use any expression for the constructor and pass arguments. It can be implemented...

This branch https://github.com/davazp/jscl/compare/ffi-improvements contains code to be able to use cl::this from Lisp. It binds the variable in the prelude of every function, outside of any function introduced by the...

I think we do not have anything like this. We should provide this and some other helper functions. They can be defined in `src/ffi.lisp`. I would like to discuss the...