Importing Segment in an Observable Model results in KeyPath conflict

[ay8s]

Describe the bug
Importing the Segment SDK in a SwiftUI Observable model causes a compiler crash due to a naming conflict with Swift’s built-in KeyPath type. Segment defines a public struct KeyPath in its codebase, which is picked up during Swift macro expansion, leading to a fatal error:

Cannot specialize non-generic type 'KeyPath'

This breaks any use of Swift’s new Observable macro in the same file.

To Reproduce
Steps to reproduce the behavior:

1. Create a SwiftUI Project with an Observable Model
2. Import Segment
3. Compile the project

Expected behavior
Project should compile successfully without failing due to internal name conflicts.

[bsneed]

Can you can use the module name to specify? ie: SwiftUI.KeyPath

[ay8s]

I don't believe so, the code is generated automatically by the Swift Macro @observable.

[ay8s]

Here's an example project.

SegmentExample.zip