new_object behaviour in ooplib
When trying to create a new object via new_object/3, there appears to be a strange behaviour when using java.lang types, namely
?- new_object('java.lang.Double', , X).
fails complaining that there is no constructor in kotlin.Double accepting a Float, BigInteger or Double as argument. The same occurs trying other Java types, such as Integer or String.
Of course kotlin types do not have such constructor, but here the fully qualified class name was used, specifying the java Double class, not the kotlin one: so, the Java class should be selected by the oop library and that class does have such a constructor. However, 2p-kt seems to ignore this and default to the homonimous kotlin class. Such a behaviour appears both counter-intuitive and potentially problematic, as it is shadowing a Java class.