4 ms·
CL doesn't have a truly standard way of writing async/multi-threaded code. Every (practical) implementation supports native OS threads, and Bordeaux threads sup
by Jtsummers 5y ago
CL doesn't have a truly standard way of writing async/multi-threaded code. Every (practical) implementation supports native OS threads, and Bordeaux threads supports every reasonable implementation while providing a uniform way to access their lower level (and implementation specific) versions. You can get good async/multithread performance out of Common Lisp. But it's, by definition, non-standard. Node at least made asyncio a part of its standard implementation, so you're not having to pick and choose or construct it from lower level primitives. There are other higher level concurrency libraries for CL that build on BT and the lower level primitives to remove the need for you to think about it, but they're still non-standard.
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.
- bestcoder69 5y ago> 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! 0: https://en.wikipedia.org/wiki/Common_Lisp#History https://en.wikipedia.org/wiki/Common_Lisp#History
- gibsonf1 5y agoWe 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. https://lparallel.org/ https://lparallel.org/ https://github.com/gwkkwg/cl-containers https://github.com/gwkkwg/cl-containers