Re:Why Turtl switched from Common Lisp to JavaScript (2019)
by gibsonf1 on Wednesday October 27, 2021 @05:20PM
(#29019291)
We simply use lparallel with incredible results. We combine that with using a thread-safe version of cl-containers, such that we save futures in a container, and then when needed, force the futures in the entire container.
Re:Why Turtl switched from Common Lisp to JavaScript (2019)
by bestcoder69 on Wednesday October 27, 2021 @02:54PM
(#29017482)
> if CL were to get a second standard
Huh, TIL. Checking wiki, the final/current version is from 1994[0]. Welp, that explains it for me. Thanks!
That's all missing from CL as a part of the standard, if CL were to get a second standard something like that would almost certainly make it into the revision. But it's not getting another standard any time soon.