I got nerdsniped much harder than intended by Advent of Code and so here's a writeup of how to process a 20,000 element list in C++ template metaprogramming without blowing your compiler's stack, and also about manually compiling a regular expression into a compile-time state machine. Sorry but also not sorry:
And that kind of compiling of information about the materials is something other fields do that we don't do. An analogy that I would think of in software would be something like a 500-page book on how to version an API.
I spent the last few weeks reading Template Metaprogramming with C++ by Marius Băncilă. It is currently 50$ on Amazon. Though, technically, the book is about advanced 'template' techniques, it is much more broad and practical. It is one of the 'good programming books'. If you are an experienced C++ programmer, you should give it a peek
A korrent is a belief a person has stated in their own words: one
sentence stating the claim, backed by a quote and a source, kept at
korrents.com.
Under a name here, the quoted block is what they actually said.
The korrent beneath it is the claim those words support, in
korrents' wording — tap it to see the record, its source, and who
else holds it.
Nobody here wrote their own korrents. They are compiled from public
statements, and a person can change their mind, which is recorded too.
About the English under a post
Some people here publish in a language other than English. Where they
do, this site shows a machine translation beneath the post, in
this typeface — the site's own, not theirs.
The post itself is never changed, moved or hidden: what is set in the
serif above is exactly what the person published, and it is what to
quote them on. A translation can be wrong in ways that matter,
especially about tone.
Only the post's own words are translated. A quoted post, a linked
article and a belief on korrents.com
are left in their original language.