Description
We have some compilation errors while generating tests for user's code when we need to generate our hardcoded util methods (like deepEquals, etc) that use classes with simple name collisions (like kotlin.Array and java.lang.reflect.Array). To fix this problem, we need to always use a fully qualified name for all classes used in util methods (except classes from the java.lang package).
To Reproduce
Steps to reproduce the behavior:
The easiest way to reproduce is by generating Kotlin test that has to use both arraysDeepEquals and createArray util methods.
Expected behavior
Correct test without compilation errors.
Actual behavior
Compilation errors because of simple name collisions (kotlin.Array and java.lang.Array).
Description
We have some compilation errors while generating tests for user's code when we need to generate our hardcoded util methods (like deepEquals, etc) that use classes with simple name collisions (like
kotlin.Arrayandjava.lang.reflect.Array). To fix this problem, we need to always use a fully qualified name for all classes used in util methods (except classes from thejava.langpackage).To Reproduce
Steps to reproduce the behavior:
The easiest way to reproduce is by generating
Kotlintest that has to use botharraysDeepEqualsandcreateArrayutil methods.Expected behavior
Correct test without compilation errors.
Actual behavior
Compilation errors because of simple name collisions (
kotlin.Arrayandjava.lang.Array).