## Fix Swift overloads producing uncompilable Java wrappers

[Clemo97]

Fixes #526

Problem

Swift allows method overloading using parameter labels (argument labels), where methods can have the same base name but different parameter labels:

public func takeValue(a: String) {}
public func takeValue(b: String) {}

In Swift, these are distinct methods because parameter labels are part of the function signature. However, when translated to Java, both were being generated with the same signature, causing compilation failures:

public void takeValue(String) //   Compilation error: duplicate method

Error:

error: method takeValue(String) is already defined in class OverloadSample

Solution

Modified the Java method name generation in FFMSwift2JavaGenerator+JavaTranslation.swift to append parameter labels as suffixes, creating unique method names that preserve Swift semantics while ensuring valid Java code.

Implementation:

• Parameter labels are joined with underscores (e.g., _a, _b)
• Applied consistently to all methods (functions, initializers)
• Getters and setters are excluded to maintain property access patterns

Example transformation:

// Swift
public func takeValue(a: String) {}
public func takeValue(b: String) {}

// Generated Java (Before)
public void takeValue(String a) //   Duplicate!
public void takeValue(String b) //   Compilation error

// Generated Java (After)
public void takeValue_a(String a) //   Unique
public void takeValue_b(String b) //   Compiles successfully

Changes

• Sources/JExtractSwiftLib/FFM/FFMSwift2JavaGenerator+JavaTranslation.swift: Added logic to append parameter labels to method names for disambiguation
• Samples/SwiftJavaExtractFFMSampleApp/src/main/java/com/example/swift/HelloJava2Swift.java: Updated sample code to use new method naming convention (e.g., globalTakeInt_i(), init_len_cap())
• Samples/SwiftJavaExtractFFMSampleApp/Sources/MySwiftLibrary/OverloadSample.swift: Added test cases with overloaded methods.

[ktoso]

Thanks for the request.what’s a reasonable direction however we should only be doing this if we detect a method has conflicts, otherwise it could be pretty annoying. Many members don’t have overloads and we can still call them with her normal names after all.

[ktoso]

Yeap still missing the required logic.

[ktoso]

marking as requesting changes