Sergej Jaskiewicz
f26e470e80
For some reason type parameters end up in `GlobdalDeclarationTable`, and thus we tracked them in `IdSignatureClashDetector`, which wasn't right and confused the diagnostic renderer that uses `org.jetbrains.kotlin.resolve.MemberComparator` for sorting the declarations to display in diagnostics. That comparator doesn't know jow to work with type parameters. Besides, type parameters, like many other types of declarations, are not considered public wrt KLIB ABI, so there's no need to show CONFLICTING_KLIB_SIGNATURES_ERROR for them. ^KT-65723 Fixed
Running tests
- To run all tests, use
./gradlew :native:native.tests:test. Please note, this Gradle task is available only in development environment and it not available at CI server. - To execute certain tests only, use the appropriate Gradle tasks. Example:
./gradlew :native:native.tests:codegenBoxTest - To execute InteropIndexer tests for all targets, use:
for TARGET in android_x64 android_x86 android_arm32 android_arm64 \
ios_arm32 ios_arm64 ios_x64 ios_simulator_arm64 \
linux_x64 linux_arm64 linux_arm32_hfp linux_mips32 linux_mipsel32 \
macos_x64 macos_arm64 \
mingw_x86 mingw_x64 \
tvos_arm64 tvos_x64 tvos_simulator_arm64 \
wasm32 \
watchos_arm32 watchos_arm64 watchos_x86 watchos_x64 watchos_simulator_arm64 watchos_device_arm64
do
echo $TARGET
./gradlew :native:native.tests:interopIndexerTest -Pkotlin.internal.native.test.target=$TARGET
done
- To re-generate tests, use
./gradlew :native:native.tests:generateTests
For more details see Testing.