konsti a6dfd3953a Handle universal vs. fork markers with ResolverMarkers (#5099) ... * Use a dedicated `ResolverMarkers` check in the fork state. This is better than the `MarkerTree::And(Vec::new())` check. * Report the timing correct naming universal resolution instead of two spaces around an empty string when there are no markers. * On resolution error, show the split that we're in. I'm not sure how to word this, since we're doing a universal resolution until we fork, so the trace may contain information from requirements that are not part of this fork.		2024-07-17 18:59:33 +02:00
..
src	Handle universal vs. fork markers with ResolverMarkers (#5099)	2024-07-17 18:59:33 +02:00
Cargo.toml	Change "toolchain" to "python" (#4735)	2024-07-03 07:44:29 -05:00