Do you need to throw an Int into the model for this?

I cannot test at the moment, but have not found documentation on this yet. I don't have a sense of how ModelContainer works across targets. I have not, for example, seen a project with SwiftData unit tests yet.

For example, List and ForEach don't give warnings when hash collisions occur. So what's the need; why require something with a Hashable value, rather than just something that is itself Hashable? At what point will SwiftUI fail due to collisions? I understand the flexibility of having a protocol to add indirection to a hashable property, but why don't we have overloads that directly support Hashable-element collections ?