Stack Overflow is changing the wording of some of its close messages. For example, "unclear what you're asking" is now "needs detail or clarity". https://meta.stackexchange.com/questions/337013/new-post-notices-rollout-on-stack-overflow
Definitely seems like a positive step.
miniblog.
Related Posts
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?
Some delightful examples of good compiler error messages in the latest Gleam release:
I'm increasingly doubtful that commit messages should be entirely immutable.
I sometimes find myself editing or commenting on merged pull requests, to help future readers.
Phabricator appended a URL to commit messages, which helped. In principle PR merging could do the same thing.