I remember Josh Bloch telling a story in some interview about how he left this out of the Java APIs and had some co-worker grumble about the "axiom of choice". He later regretted the decision and thought it would often be a useful method, but I don't know what his reasons were.
Are there plans to optimize kotlin reflection, since its slower than java reflection.
4 years ago
And also maybe add a function that takes a class's superclass as a KClass and all implemented interfaces as a List<KClass>
I already got an easy algorithm for both based on the class.superclasses and it might be easier just implementing it to kotlin-reflect