To be fair a lot of that downloading and building was for the stuff required to compile Rust to WASM and generate the bindings required to run it from JS in node.js and in the browser. Did you tried starting the server.py and visiting the anagram page it serves up?Much to my astonishment... automatically downloaded, compiled and installed 63 crates.
Also, in the C/C++ I would have had you downloading HashBrown and other bits and bobs manually from their git repos and building/installing them. Or I might have provided a BASH script to do all that, which would have failed as such things usually do. The Rust Cargo package manager is brilliant in that respect.
You have discovered my secret weapon there. You see HashBrown is a go faster hash table in C++ from Google that somebody converted to Rust. The presenter in that video is Matt Kulukundis from Google. He probably wrote the original HashBrown!Have you watched this presentation about cache-friendly hash tables?
I saw that video a long while ago, didn't pay much attention, what would I do with a hash table? I'll have to watch again now.
I was wondering what the execution time printed by main.rs is on the encabulator is. It's getting to the point that reading the file and writing the output is a significant part of the time reported by "time".