Michał "phoe" Herda

There is the rationale from https://bugs.launchpad.net/sbcl/+bug/1909800 that is convincing to me: > Adding :extensible-sequences now would mean all older SBCL will stop supporting it. Perhaps it would be better for...

> `subtypep` is permitted to return the values false and false only when at least one argument involves one of these type specifiers: `and`, `eql`, the list form of `function`,...

https://gitlab.common-lisp.net/alexandria/alexandria/-/issues/26 was created, let's see how this goes.

Weird. https://github.com/armedbear/abcl/blob/36a4b5994227d768882ff6458b3df9f79caac664/src/org/armedbear/lisp/Lisp.java#L515-L516 If a thread is marked to be destroyed, then a Java error (not an exception) is eventually thrown. That should unwind the stack and therefore should execute `unwind-protect`...

A solution that should always work, but that would change the architecture of destroying threads, would be to implement destroying a thread via interrupting it with `(lambda () (throw '%abcl-destroy-thread...

Two cents from me: I don't care much for package autocompletion since my interactive package traversal happens mostly via the slime REPL shortcut `,in` and via `C-c ~`; as for...

I guess it's about a) keeping keyword syntax completions minimal and b) microoptimizations, since you can't portably unintern a keyword without UB.

> to determine things Which sort of things?

I can reproduce this issue. It seems like Drakma has established a connection but fails to receive any incoming data. REPL: ```lisp CL-USER> (setf drakma:*header-stream* *standard-output*) # CL-USER> (drakma:http-request "https://health.usnews.com/doctors/carolyn-connelly-544761"...

I can still reproduce this on SBCL 2.2.2 and the recent quicklisp dist. I have no idea if the issue lies on Drakma side or the CL+SSL side. But timeouts...