Repository navigation
jextract issues with nested types that share the same name #822
Description
my environment:
swift-java: main @ c235a0f
swift-java-jni-core: main @ b440a0be98381550cf189c903782e817619ffa05
using swift 6.3.3 and im using the jni mode.
my module contains several nested types which share the same name. example 1 example2
reproduced with this snippet.
public struct Outer: Sendable, Codable {
public enum Kind: Sendable, Codable {
case alpha
case beta
}
}
extension Outer {
public struct Inner: Sendable, Codable {
public struct Innermost: Sendable, Codable {
public enum Kind: Sendable, Codable {
case x
case y
}
public var kind: Kind // Outer.Inner.Innermost.Kind
public init(kind: Kind) {
self.kind = kind
}
}
public var innermost: Innermost
public init(innermost: Innermost) {
self.innermost = innermost
}
}
}the jextract plugin doesn't produce fully qualified types. in my own package, it had issues with DiscordChannel.Message.MessageReference.Kind which became DiscordChannel.Kind. in the above snippet its like Outer.Inner.Kind becoming Outer.Kind. i think its specifically for extensions.
the repo i'm working on is available here:
https://github.com/llsc12/Paicord/tree/android-2
thank you!
Metadata
Metadata
Assignees
Labels
No labels
Activity
ktoso commentedon Jul 9, 2026
Thanks for the report, I'll have a look what's up
llsc12 commentedon Jul 9, 2026
i'm also lightly looking into it and i think there's quite a few layers of issues before my swift package will be buildable with swift-java. hmm
ktoso commentedon Jul 9, 2026
Fix incoming here #823
Improve nested names handling even in #if scopes
llsc12 commentedon Jul 9, 2026
thank you very much!
Improve nested names handling even in #if scopes
ktoso commentedon Jul 9, 2026
I also checked the extension case you had, please check current main!