Add known limitation for nested property intersection types

[mmkal]

See mmkal/expect-type#21 (comment) for (lots of!) context

[changeset-bot]

⚠️ No Changeset found

Latest commit: fa351af

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[unional]

Thanks, that is definitely a limitation. If we do that recursively, it will lead to infinite loop when there are recursive types.

Here, I take the stands that { a: 1 } & { b: 1 } == { a: 1, b: 1 } as in type category they are just two representations of the same category. Thus when doing comparison they should be treated the same.

There can be a IsStrictEqual type that excludes union and intersection check if there are such use case.