[Openmcl-devel] type specifier '(simple-vector n) in defmethod

[R. Matthew Emerson]

> On Jan 5, 2024, at 12:42 PM, Nicolas Martyanoff <nicolas at n16f.net> wrote:
> 
>> CCL is a highly optimized, complex-but-lean, "diamond."
>> I back the "diamond" approach.
> Dropping all the MacOS UI code, the editor, cleaning the mess (I still
> have headaches from what I've read on the FFI layer and error handling
> in the IO layer) concentrating on standard compliance and robustness
> would make it a diamond in time. The amount of work to get there is
> staggering; I suspect writing a new implementation (with a decent
> userland thread based runtime pretty please) would be less painful and
> much more interesting.

What do you mean by a “userland thread based runtime”?  Does that mean that you would prefer cooperatively-scheduled / coroutine style Lisp processes (like old MCL had)?

Dealing with preemptively-scheduled OS threads is a pain, but multicore processors are extremely common, and it seems important for Lisp to be able to make use of them.

Anyway, I appreciate that parts of CCL are old and grotty. I can understand the urge to burn it all down and start over in order to do everything right. But there are things about CCL that I like, too.