bordeaux-threads
prechelt-phone-number-enco
| bordeaux-threads | prechelt-phone-number-enco | |
|---|---|---|
| 6 | 3 | |
| 222 | - | |
| - | - | |
| 5.9 | - | |
| 18 days ago | - | |
| Common Lisp | ||
| MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
bordeaux-threads
- SBCL THREAD - Difficulty Understanding the Error Message
-
For serious/industrial/business use, in what ways do you think Common Lisp beat Clojure, and vice versa?
This got me wondering. After a few mins of web searching, I hit upon the Bordeaux Threads project multiple times: https://github.com/sionescu/bordeaux-threads
-
bordeax-threads (2) works with garnet & lispworks
About bordeax-threads API v2
-
Learning Common Lisp to beat Java and Rust on a phone encoding problem
common lisp supports type annotations. there is even an ML-type language impletmented in it (see coalton). quick lisp [1] is used for package managment, bordeaux-threads [2] for threading.
1. https://www.quicklisp.org/index.html
2. https://github.com/sionescu/bordeaux-threads
prechelt-phone-number-enco
-
Optimising Common Lisp to try and beat Java and Rust on phone encoding 2/2
> it’s using Unicode-aware string stuff
Rust uses UTF-8 internally for Strings, so it's very efficient to parse a file into a String, then using slices to go through it... this is probably the best you can get as parsing ASCII input as UTF-8 is very efficient (the 0-bit is always zero in ASCII, the unicode decoder only needs to check that's the case for every byte, so it's not some kind of complicated computation it's doing to decode)...
If you use bytes for everything, you will make the whole code much harder to follow and it still won't run faster.
Check for yourself: https://github.com/renatoathaydes/prechelt-phone-number-enco...
-
Learning Common Lisp to beat Java and Rust on a phone encoding problem
This is a pretty introductory CL article, mostly a commentary on Norvig's solution to the problem. Still, I learned about the #. readmacro from it. The conclusion: "[The Lisp implementation] was the fastest implementation for all input sizes except the largest one, where it performed just slightly worse than my best Java implementation." GH repo at https://github.com/renatoathaydes/prechelt-phone-number-enco.... Sounds like he was mostly measuring the performance of the SBCL bignum implementation.
-
How to write slow Rust code
source: https://github.com/renatoathaydes/prechelt-phone-number-enco...
What are some alternatives?
woo - A fast non-blocking HTTP server on top of libev
jelm - Extreme Learning Machine in J
prechelt-phone-number-encoding - Comparison between Java and Common Lisp solutions to a phone-encoding problem described by Prechelt
cl-cookbook - The Common Lisp Cookbook
prechelt-phone-number-encoding - Comparison between Java and Common Lisp solutions to a phone-encoding problem described by Prechelt
snabl - a simple Go scripting language
ulisp - A version of the Lisp programming language for ATmega-based Arduino boards.
coalton - Coalton is an efficient, statically typed functional programming language that supercharges Common Lisp.