When I made changes, the API macro kept using stale cached functions on further quicklisp loads because quicklisp did not know about the dependencies and did not recompile.
Thank you! That was an interesting read, I had no idea that was how it works. I'll look into these travis fails in the next couple of days, but it looks like they have nothing to do with your commit.
When I made changes, the API macro kept using stale cached functions on further quicklisp loads because quicklisp did not know about the dependencies and did not recompile.
Discussed around here: https://irclog.whitequark.org/lisp/2017-11-20#20592787