Do not replace Map.of() by Collections.emptyMap()

[C-Otto]

My code always returns an empty map, implemented using Map.of(). When running pitest, this is mutated to return Collections.emptyMap() instead. As I don't have any test that would be able to see the difference, this mutation survived.

Please treat Map.of() the same as Collections.emptySet(), i.e. do not try to mutate one into the other.

Version 1.9.9.

[hcoles]

The EquivalentReturns filter already catches List.of and Set.of, not sure why Map.of was missed. Will be fixed in the next release.

[C-Otto]

You added the "Collections.emptyMap()" return value in 89b0c2c, after Set.of() and List.of() were already known as "empty" equivalent.

[hcoles]

Released in 1.9.10