SkieWarning.NameCollision as Error

[ProVir]

Hi!

In case of collisions, SKIE writes warning during assembly, but this usually goes unnoticed by developers.

Is it possible to add a flag that will terminate the build of the project with an error in case of collisions?

Thanks!

[FilipDolnik]

Hi! Skie currently does not support this, but it should be a straightforward feature to add. I will convert this issue into a discussion where we track feature requests.

[wd-jacob-kwitkoski]

Bumping this - we just hit exactly this gap.

We scope SuppressSkieWarning.NameCollision(true) to a known allowlist of fully-qualified class names that have an intentional, accepted Swift-name collision (e.g. a Kotlin description property colliding with the bridged CustomStringConvertible.description). The point of scoping it narrowly rather than suppressing globally is so that a new colliding declaration in a class we haven't reviewed still produces a warning, giving the team a chance to decide whether the auto-rename is acceptable.

In practice, though, that warning is just a log line. It's easy to miss in a long CI build log, and nothing stops a PR from merging with a new, unreviewed silent rename. We'd like the option to make that failure mode loud (CI-blocking) rather than relying on a human noticing a warning.

It's worth noting that: kotlin.allWarningsAsErrors / -Werror doesn't help here either, since these are emitted during SKIE's own Swift-generation step rather than through the Kotlin compiler's diagnostic pipeline. This was confirmed in our build (had allWarningsAsErrors = true already set, and a NameCollision warning still didn't fail the build).

One possible API shape - a build-level opt-in:

skie {
    features {
        warningsAsErrors.set(true) // fails the build if any non-suppressed SKIE warning is emitted
    }
}

or, more granular, extending the existing per-group configuration to a three-state severity instead of a boolean suppress flag:

skie {
    features {
        group {
            NameCollision(WarningSeverity.Error) // Warn (default) | Suppress | Error
        }
    }
}

I'm happy to defer to however you'd design it. Either would let teams enforce "no new unreviewed Swift-name collisions" as an actual CI gate, rather than something that depends on someone reading build output.

Environment:

• SKIE 0.10.12
• Kotlin 2.3.21