Alejandro Zamora Fonseca

Hi! You are welcome :) Don't know if this will be possible because some of the functions added previously to `abcl.lisp` call to the main package, creating a circular dependency....

I also got the same error when trying to compile and load a file with something like this: `(defparameter *some-hash-table* #.(make-hash-table :test 'equalp))` The compiled .abcl file result was like:...

Maybe an idea to solve this is to follow the CLISP approach, they print hashtables in a readable way, using structuctures: The CLISP output for this snippet is: `(|SYSTEM|::|VERSION| '(20100807.))...

I'm not a 100% sure of this but I've been reading the standard for [subtypep](http://clhs.lisp.se/Body/f_subtpp.htm) and it seems that this behaviour is allowed. 

Yes maybe they should change it. And also, maybe add some conditional warning inside the code of **alexandria:type=** when any of these type identifiers are used in at least one...

Hi, I successfully quick-loaded _fset_ with last ABCL master, commit fff48abd8d2821b53d73015c1c42ecb8139a946d following steps in the Readme using quicklisp-abcl in Ubuntu 18.04. Maybe this issue is solved after latest versions of...

Please forget my last comment. It is still happening. Probably I was confused when running other CL implementation Anyway, I'm trying to solve this issue.

This commit [4a3730af](https://github.com/alejandrozf/abcl/commit/4a3730af2b07048ff2fea237a3e52adb14141498) makes possible to compile _fset_ library, the same approach can be used for _cl:compile_ but this breaks the CL standard by making functions inside these forms interpreted...

I think this issue can be closed, the fix was merged to master. See [https://github.com/armedbear/abcl/pull/490](https://github.com/armedbear/abcl/pull/490)

I was able to compile and run Maxima with this commit d417a58a I didn't have time yet to check if this is not introducing regressions to ABCL but a few...