phoenix384

In my opinion forcing rules to be non-static was an annoying change and an absolutely unnecessary restriction. I can do it anyway by e.g. assigning the value of the static...

An example could be a matcher for Selenium WebElements that matches if a WebElement has a specific text. matchesSafely would look like this ``` protected boolean matchesSafely(WebElement item, Description mismatchDescription)...

Why not avoid calling matchesSafely twice like this? ``` public abstract class TypeSafeDiagnosingMatcher extends TypeSafeMatcher { private Description mismatch; @Override protected final void describeMismatchSafely(T item, Description mismatchDescription) { if (mismatch...

It's not a problem in the test design. It's a problem that is quite normal to Selenium tests. And I don't want to observe anything changing over time - I...