Empty array initialization `[TypeName]()` causes build error in Swift 6 with cross-module types

[kuritatu18]

Problem

When mockolo generates a mock for a protocol method that returns an array, it uses the syntax [TypeName]() for the default return value. This causes a build error in Swift 6 when the type is defined in another module and doesn't have a publicly accessible initializer.

Environment

• mockolo version: 2.4.0
• Xcode version: 26.0
• Swift version: 6.2

Steps to Reproduce

1. Define a struct in Module A without a public parameterless initializer:

// Module A
public struct SomeModel: Sendable {
    public let id: String

    public init(entity: SomeEntity) {
        self.id = entity.id
    }
}

2. Define a protocol in Module B that returns an array of this type:

// Module B
/// @mockable
public protocol SomeRepository: Sendable {
    func fetchItems(ids: [String]) -> [SomeModel]
}

3. Run mockolo to generate mocks (Mock module imports Module A and Module B)
4. Build the Mock module

Generated Code

public func fetchItems(ids: [String]) -> [SomeModel] {
    let handler = handlerState.withLock { state in
        state.callCount += 1
        return state.handler
    }
    if let handler = handler {
        return handler(ids)
    }
    return [SomeModel]()  // ❌ This line causes the error
}

Build Error

error: cannot call value of non-function type '[SomeModel.Type]' (aka 'Array<SomeModel.Type>')

Expected Behavior

mockolo should generate [] instead of [TypeName]() for empty array default values:

return []  // ✅ Works correctly - type is inferred from return type

[sidepelican]

Isn't it problem that SomeRepository uses SomeModel without importing its module?
This could become an issue in future versions of Swift.

Alternatively, use the --custom-imports option.

[kuritatu18]

I apologize for the lack of clarity in my explanation. SomeRepository does include import ModuleA, and when generating the mock, I am using the option --custom-imports ModuleB.
The resulting generated Mock file correctly includes both import ModuleA and import ModuleB.

[sidepelican]

I cannot reproduce this issue.
Are there any Swift packages where this issue can be reproduced?