Alex Waygood f85ea1bf46 [red-knot] Ensure differently ordered unions and intersections are understood as equivalent even inside arbitrarily nested tuples (#15740) ... ## Summary On `main`, red-knot: - Considers `P | Q` equivalent to `Q | P` - Considered `tuple[P | Q]` equivalent to `tuple[Q | P]` - Considers `tuple[P | tuple[P | Q]]` equivalent to `tuple[tuple[Q | P] | P]` - ‼️ Does _not_ consider `tuple[tuple[P | Q]]` equivalent to `tuple[tuple[Q | P]]` The key difference for the last one of these is that the union appears inside a tuple that is directly nested inside another tuple. This PR fixes this so that differently ordered unions are considered equivalent even when they appear inside arbitrarily nested tuple types. ## Test Plan - Added mdtests that fails on `main` - Checked that all property tests continue to pass with this PR		2025-01-25 16:39:07 +00:00
..
resources	[red-knot] Ensure differently ordered unions and intersections are understood as equivalent even inside arbitrarily nested tuples (#15740)	2025-01-25 16:39:07 +00:00
src	[red-knot] Ensure differently ordered unions and intersections are understood as equivalent even inside arbitrarily nested tuples (#15740)	2025-01-25 16:39:07 +00:00
tests	mdtest: include test name in printed rerun command (#14684)	2024-11-30 11:01:06 +00:00
build.rs	Modernize build scripts (#13837)	2024-10-20 22:35:35 +01:00
Cargo.toml	type: ignore[codes] and knot: ignore (#15078)	2024-12-23 10:52:43 +01:00
mdtest.py	[red-knot] Fix possible TOCTOU mistake in mdtest runner (#15673)	2025-01-22 15:24:25 +00:00
mdtest.py.lock	[red-knot] Markdown test runner (#15632)	2025-01-21 14:06:35 +01:00