From ad18d5984bc43028111e7d29a068e59c6b1b1e9b Mon Sep 17 00:00:00 2001 From: Svyatoslav Scherbina Date: Tue, 11 May 2021 10:30:57 +0300 Subject: [PATCH] Expand comment for unsupported nested generics when exporting to Swift Add links to Swift and Kotlin issue trackers. --- .../kotlin/backend/konan/objcexport/ObjCExportNamer.kt | 2 ++ 1 file changed, 2 insertions(+) diff --git a/kotlin-native/backend.native/compiler/ir/backend.native/src/org/jetbrains/kotlin/backend/konan/objcexport/ObjCExportNamer.kt b/kotlin-native/backend.native/compiler/ir/backend.native/src/org/jetbrains/kotlin/backend/konan/objcexport/ObjCExportNamer.kt index a4e7772474b..e2de7759860 100644 --- a/kotlin-native/backend.native/compiler/ir/backend.native/src/org/jetbrains/kotlin/backend/konan/objcexport/ObjCExportNamer.kt +++ b/kotlin-native/backend.native/compiler/ir/backend.native/src/org/jetbrains/kotlin/backend/konan/objcexport/ObjCExportNamer.kt @@ -220,6 +220,8 @@ private class ObjCExportNamingHelper( private fun T.canBeSwiftInner(provider: ClassInfoProvider): Boolean = when { objcGenerics && provider.hasGenerics(this) -> { // Swift compiler doesn't seem to handle this case properly. + // See https://bugs.swift.org/browse/SR-14607. + // This behaviour of Kotlin is reported as https://youtrack.jetbrains.com/issue/KT-46518. false }