Ansgar Konermann

Kotlin SAM overload resolution ambiguity between `Consumer` and `ThrowingConsumer`

32

#### Summary When using AssertJ Core 3.21.0 from Kotlin, an overload resolution ambiguity occurrs for methods having overloads which accept both Consumer and ThrowingConsumer. Methods affected (list noncomprehensive) ``` org.assertj.core.api.AbstractAssert#satisfies(java.util.function.Consumer

Ensure code in master branch follows coding standards and formatting

8

Found org.fest.assertions.internal.Arrays#assertHasSameSizeAs() No formatting applied at all. Goal: - define at least formatting rules - apply them automatically before each commit - don't accept code which does not follow formatting...

Ensure all commits can be traced back to their contributors, so we have a chance of contacting the original authors

1

Found code lines with user name "unknown" Example: FEST-Assert commit 2862f1e9e66e43a716ce5a3fe150d64fdcd80169 Author: unknown If we can't reach the authors, we might run into serious trouble when proving "IP Clearance". See:...

Document "data snapshot" aspect/intent of AbstractDbData and subclasses more explicitly

1

Dear AssertJ-DB team, Dear Joel, I found one of my friends wrapping Table to allow for a "data reload feature". As I understand the JavaDoc of that class, the intended...