Jon Ross-Perkins 2e4beaf8f0 Canonicalize struct types. (#2855) ...

This adds canonicalization of struct types based on their type fields. It obsoletes the current CanImplicitAsStruct because the type ids should now be identical when they're structurally identical; there's only a reason to implicit CanImplicitAsStruct to detect _compatible_ conversions.

The type fields themselves aren't canonicalized because it would need to be done during the first parse, and could yield name conflicts being associated with the wrong location. i.e.:

```
var x: {a: i32, a: i32};
var y: {a: i32, b: i32, a: i32};
```

This should yield two separate name conflict diagnostics pointing at the type fields for each respective line, but if struct type fields were canonicalized then both would point at the first `a: i32` field definition. This isn't expected to be an issue for types because I'm trying to print those, but we may also end up with a "first defined at" situation in some cases (still, less confusing because the type should match). Regardless, I think individual fields gets much more awkward.

2023-05-26 14:42:45 -07:00

..

call

Canonicalize struct types. (#2855)

2023-05-26 14:42:45 -07:00

definition

Switch types to a SemanticsTypeId. (#2854)

2023-05-26 11:19:49 -07:00