Viewing profile — kscarlet

So does the community of every other dialect (Common Lisp, at least). Write a function if you don't have to write a macro, and maybe declaim the function to be inlined. The "Lisp C…

VSCode: https://github.com/kchanqvq/olive

PSA: VSCode users deserve to use the OLIVE plugin ( https://github.com/kchanqvq/olive ).

Honestly I think the author misunderstood and misused P != NP. They should have said something like "collusion is NP-hard". P = NP doesn't imply NP-hard problem is efficiently solv…

These mean nothing. The C/C++ implementations use SIMD intrinsic while Lisp doesn't (it should have used sb-simd).

That's what the author means. She know what she's talking about.

> A small but illustrative example: given a live running clisp program, I can click on a UI element to inspect both the live object and the underlying code in the IDE. I can even c…

Can you tell a bit more about what is missing from Emacs SLIME when compared to LispWorks?

I don't see any comments on Kernel in the post. I didn't waste my time reading the book, but the post criticizes unhygiene F-expr, which is known to be awful and is exactly what Ke…

Not directly. Every "extensions" listed above cannot be implemented as user libraries, that's why these back and forth process between implementation extensions and portability use…

I think the Common Lisp ecosystem sets a good example of how a dozen of implementations move ahead together. Implementations experiment with extensions, the really useful ones get …

(defparameter *a* '(1 2 3)) (setf (car *a*) 3) And this is undefined behavior because it mutates literal constant. I stopped reading further. The CL column is so bad.

"Lisp Curse" is really a myth, or at least, it completely fails to apply to the Common Lisp community. https://applied-langua.ge/posts/lisp-curse-redemption-arc.ht...

Why? Many Lisp systems and Common Lisp in particular have great hot reloading capability, from redefining functions to UPDATE-INSTANCE-FOR-REDEFINED-CLASS to update the states.

Very nice. p.s. (I hate to point this out), there seems to be a name collision with https://lisperator.net/slip/

> As to the actual difference between JIT vs. AOT... it may just come down to accounting. That is, on whether you can always exclude the compilation time/cost from the overall prog…

They generate native machine code.

In that sense almost every compiled Lisp/Scheme implementation, GHC, etc. or any other interactive programming system, count as JIT. But virtually nobody in those circles refer to …

It seems that JIT is overloaded with at least 2 meaning. The canonical definition of JIT is "compilation during execution of a program". Usually, a program is being interpreted fir…

I guess this case is workable similar to struct redefintion. There can be a condition and a CONTINUE restart, which makes instances of the removed constructor obsolete.

I don't find any good idea in [1]. > 1. The function and variable namespaces have been collapsed into a single namespace. Lisp-N, package system and homoiconic macro is a local opt…

wookie is built on cl-async, so my hope is that it's more tractable to write proper async SSE handler. But I haven't looked at whether it's possible to keep open connection asyncly…

> Each SSE connection blocks one worker for its entire duration. Have you tried wookie? Such extreme case of blocking the event loop... negates any benefit of async processing.