Consider calling state.Action#precondition, state.Action#transformer without reflection

[vlsi]

Testing Problem

I'm trying the new API from #134, and I see jqwik calls state.Action methods via reflection.
It makes it harder to understand the stacktrace.

Suggested Solution

Call interface methods without reflection.

Discussion

Is reflection needed there?
I do understand the reflection might help the engine to verify if the class has a non-trivial method implementation, however, I believe calling the method via reflection is both easier to understand, faster, and less prone to errors.

[vlsi]

PS. I'm not sure this is an issue, and it looks like GitHub Discussions might be better for these types of "issues".

[jlink]

Why does the reflective call bother you? It's not called so often that a performance problem is likely.

Reflection is currently necessary to determine if the methods at hand are overridden. The subsequent call of the overridden method could, I assume, be done statically.

[vlsi]

Why does the reflective call bother you? It's not called so often that a performance problem is likely.

Stacktraces become harder to understand.
"find usages" does not show reflective usages.
The code is harder to follow.

The subsequent call of the overridden method could, I assume, be done statically.

That is exactly my suggestion.

[jlink]

Stacktraces become harder to understand.
"find usages" does not show reflective usages.

Reasonable argument.

Since Action will probably be refactored into two separate interfaces, I'll defer until this is done.

[jlink]

Has been resolved with the introduction of Action.Dependent and Action.Independent in 85f5f03