*Amazing* blog post on modelling compilers as a search problem on a Value State Dependence Graph: https://jamey.thesharps.us/2017/06/search-based-compiler-code-generation.html
Related Posts
One advantage I've come to appreciate about Dash/Zeal docsets: it's really nice having focused search.
The text search is constrained to the languages I care about enough to download the docset, substantially increasing the relevance. In Google I'd need to specify the language.
I've been using "Expected Int, but got String" for my type error messages, but I've been wondering if I could do better.
"Expected Int here, but this value has type String" or "This expression requires Int, but the value is String".
Do you have a favourite?
It's incredibly hard to explain adversarial problems to users. I see gamers sincerely asking "why doesn't the publisher just fix the cheater problem?".
This is exacerbated by the fact that sharing too many details of anticheat can make the problem worse.