Post #3651049

My favourite kind of bug fix: one that only adds a new regression test and does not touch any existing test. The new test proves the bug is fixed. The untouched existing tests prove the fix does not break any behaviour we rely on; at least none that is covered by a test. When a bug fix forces you to change existing tests, that is worth a pause: either the tests were coupled to implementation details, or the "bug" was actually documented behaviour someone depends on.