Stefano Cordio

> Could you advise on any workaround or point out where I might be handling the custom assertion implementation incorrectly? @AlexeyAkentyev So far, I think the issue happens only with...

Thanks for following up on this! Would you like to create a PR with the fix?

> As a solution, it will require switching from Array to List structures for any `ForProxy` method parameters. I don't see it as a problem 👍 We are already working...

Thanks for bringing this up, @Adrodoc. This is definitely something we can revisit in version 4.

> ### 3. Integration/Helper for Mockito argument matches Are you aware of Mockito's [`assertArg`](https://javadoc.io/static/org.mockito/mockito-core/5.14.2/org/mockito/Mockito.html#55)?

Related to what @jonatan-ivanov mentioned at https://github.com/uber/NullAway/issues/1219#issuecomment-2993112911: > In the meantime I found that > > ```java > assertThat(c).hasSize(1); > ``` > > has the same issue (it does an...

> It would be beneficial to express that in AssertJ somehow, so that tools like NullAway don't require a case-by-case handling. I wonder if we should define something similar to...

> AFAIK, the JSpecify team is considering a more general-purpose solution to the "contract" issue That would be nice! I couldn't quickly find a related issue in the JSpecify issue...

Thanks for the feedback, @sdeleuze! Please also consider https://github.com/uber/NullAway/issues/1224#issuecomment-3036356952, which describes why `@Contract` wouldn't cover the AssertJ use case.

Hi @cpovirk! 👋 Since Truth already uses JSpecify, is [the above topic](https://github.com/assertj/assertj/issues/3727#issuecomment-3035960270) something you already have experience with?