renatoathaydes/prechelt-phone-number-encoding
View on GitHub ↗ ★ 30 Java
Comparison between Java and Common Lisp solutions to a phone-encoding problem described by Prechelt
6 mentions on Hacker News by 5 people: 0 stories, 6 comments · first 2021-08-02 · latest 2021-10-14
20082026
-
> 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…
comment by brabel · 2021-10-14 · in Optimising Common Lisp to try and beat Java and Rust on phone encoding 2/2 -
There are two or three branches with different versions of the Rust code, and the author is using the fastest one. What you believe will make the Rust code faster won't, trust me. If you think I'm wrong, could you please submit a PR and…
comment by brabel · 2021-10-14 · in Optimising Common Lisp to try and beat Java and Rust on phone encoding 2/2 -
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…
comment by kragen · 2021-10-01 · in Learning Common Lisp to beat Java and Rust on a phone encoding problem -
It's always sad to see someone get burnt by the internet, I wish him, and also those who criticised him, well. On a brighter note, I appreciate the noob-friendly explanations. It made it really easy to follow along. I'm also really curious…
comment by jlledo · 2021-08-09 · in How to write slow Rust code – Part 2 -
> … his original code was n00btastic… Sorry, but this is at-least the second blog post, in the last week, and previously — "I've discussed the Rust and Julia versions with experts in those languages ( —— I know Rust well enough —— , but…
comment by igouy · 2021-08-02 · in How to write slow Rust code -
I don't recommend drawing too much of a conclusion from these tests, about anything other than printing in <your language>. Once the algorithm is somewhat optimized, the benchmark is completely dominated by printing to stdout, not the…
comment by lkey · 2021-08-02 · in How to write slow Rust code