BestMatchingConstructor#typesAreCompatible does type compatibility the opposite way

[rahulpilani]

On line 124 of BestMatchingConstructor.java, you have the following code:
if (!inputParamType.isAssignableFrom(constructorParamType)) { matches = false; break; }

Shouldn't this comparison be the other way? like so:
if (!constructorParamType.isAssignableFrom(inputParamType)) { matches = false; break; }
It's perfectly fine if the constructor param is a super class or an interface of the inputType, but the other way around will be a compile error. So the net effect of this is that only exact types are allowed, for which there is no work-around if the constructor param is an interface.

[rahulpilani]

#10

[davidmarquis]

Thanks! Good catch! Merging to master... do you need this quickly? If yes I can release a new revision, otherwise I'll wait for the next release.

[rahulpilani]

How far out is the next release? For now I am avoiding using it because of this issue, so I am not blocked.

[davidmarquis]

I have released https://github.com/davidmarquis/fluent-interface-proxy/releases/tag/fluent-interface-proxy-2.1.2 with your fix, enjoy!

[rahulpilani]

Awesome! thanks!