When should you use auto in C++? https://herbsutter.com/2013/08/12/gotw-94-solution-aaa-style-almost-always-auto/ argues that it's safer, more readable and more consistent.
miniblog.
Related Posts
Thinking more about the "auto eval definitions" approach, I think it breaks down when debugging. If I want to step through the existing definition, it'd be really awkward to re-evaluate the definition at my cursor.
I'm not sure how I feel about languages with auto currying.
Upside: Partial application is easy.
Downside: It's common to miss a parameter when refactoring, and errors can be unclear.
Upside: You can be generic on functions: a -> b.
Downside: An a -> b isn't very useful.
I've written a manual for Difftastic with mdbook! https://difftastic.wilfred.me.uk/
mdbook makes it super easy: it auto-creates stub files, and reloads your browser as you write. It's a really nice workflow.