This is wild: compiling SMT problems to C++ then using coverage guided fuzzing to find solutions!
miniblog.
Related Posts
I suspect there's an analogy of blub programming languages for IDEs. Once you've seen more powerful solutions you miss them in less capable tools. If you haven't learnt them, you're indifferent.
This is probably why 'table stakes for a modern IDE' viewpoints vary so much.
Sometimes it's a real pain that JSON doesn't support comments. One positive consequence is that 'npm install' is always able to programmatically add new entries.
Cargo's TOML is much harder to edit in a way that preserves comments, though solutions now exist.
I've learnt a lot from comparing notes with other #AdventOfCode people. I end up going back to old solutions and refactoring to be more idiomatic (and shorter)!