9:24:33ck_for the record, I exited the debugger and did those two steps again -- (ql:quickload :radiance), chatlog -- and it went through without issue. Maybe you need to quickload radiance two times first.
11:43:16jmercourisany projects attempt to create an elisp interpreter in cl?
11:43:41jmercourisi know the other way around has been attempted for syntactical things, cl-lib
11:44:35jmercouristhe only thing I see is this discussion I participated in a long time ago: https://www.reddit.com/r/emacs/comments/a8d61y/help_with_porting_elisp_to_cl/
11:57:50phoealso https://news.ycombinator.com/item?id=21665987 is a relevant discussion from not too long ago regarding compiling elisp
11:58:11phoemaybe #emacs will be able to tell you more about it since it is the home of elisp
12:00:00jmercouristhats an interesting discussion indeed, though a lot of the comments are parroty and 'talk to talk' type things as is common on YC
12:01:45_deathstatements like "Emacs Lisp is fundamentally simple"
12:02:34jmercourisI also love the rest of that statement
12:02:41jmercouris"But the global scope is the power. The global namespace matters. A lot."
12:02:59jmercouristhe global scope is the achilles heel of Elisp, and Emacs especially!
12:03:22jmercourisor rather the two edged sword, convenient, but very deadly, and you cut yourself a lot accidentally
12:04:24_deathhow would an elisp interpreter be helpful?.. elisp is a language for emacs, which has abstractions like buffers, windows, markers, fonts, and a ton of other things
12:04:42_deathwith that in mind, CL is a tiny language compared to elisp
12:06:02jmercourisas you might imagine, I am thinking of Next when asking this question :-)
12:06:18froggeythe obvious solution is to compile emacs to CL