Having this exposed is useful, because it allows one to very quickly disprove whether (say) a copy of an array has diverged from the original, to avoid having to laboriously compare before/after states. But an identity check is no substitute for the real `==`: two values can be (and often are) equal even if they aren’t identical.

The lack of a protocol and the lack of `isTriviallyIdentical` methods on basic scalar types like `Int` or `Bool` is simply a consequence of the niche nature of this operation, and the lack of agreement on what the protocol should look like. The Standard Library ships the operation on types where defining it outside the library would require unsafe operations and/or encapsulation violations (such as looking at the raw bytes within the representation of an instance). Having the operations allows developers to design protocols on their own, if and when they need them.