Inconsistent autocompletion results for strongly-typed macro arguments

[MahdiBM]

Description

The Swift toolchain should be able to provide full autocompletion results for macros when they're defined in a strongly-typed way in source code.

Reproduction

/// Encodes enums in a custom way.
/// The `fatalError()`s won't even be present anywhere in the code,
/// they are just to make the code compile and not require use to do e.g `default: String? = nil`.
macro CodableEnum(
    default: String = { fatalError() }(),
    conformances: [CodableEnumConformance] = { fatalError() }()
) = #externalMacro(
    module: "CodableEnumMacro",
    type: "CodableEnumMacroType"
)

When trying to annotate a type with this macro, there is no autocompletion results for e.g. CodableEnum(conformances:), but when you type that out, it'll provide autocompletion results for the elements of the array of conformances and when you e.g. write conformances: [.so] it'll show autocompletion for .something.

Expected behavior

Autocomplete like normal Swift code.

Environment

swift-driver version: 1.87.3 Apple Swift version 5.9.2 (swiftlang-5.9.2.2.51 clang-1500.1.0.2.2)
Target: arm64-apple-macosx14.0

Additional information

No response

[rintaro]

@MahdiBM Is this still an issue for you? I can't reproduce this in recent toolchians.

[MahdiBM]

I'd suspect this is solved but I can't properly test it since the project that originally had this issue no longer builds on Swift 6.1 (already reported that bug) and 6.2 nightlies. I'll close this issue and reopen later if needed.