Is `Any` unsound?

[Soni]

Continuing the discussion from Pre-RFC: sum-enums:

@H2CO3

In cases when ordering of type arguments is required it can be done based on TypeId of each type. Alternatively for tag we could use TypeId directly

Doesn’t TypeId have a non-uniqueness bug? I mean, I get that it’s a hash, but last time I read about it, IIRC some of the compiler/runtime developers warned that it has a way higher than negligible/acceptable chance of collision for realistically complex types. If this is the case, using it as a discriminant or an ordering key can cause unsoundness and memory unsafety bugs, because it would result in accidentally interpreting values as the wrong type.

Does this mean Any is unsound?

[withoutboats]

You can usually find known soundness bugs on the issue tracker

Issue: Collisions in type_id