Charlie Marsh c669542a9e Respect overrides in all direct-dependency iterators (#2742) ... ## Summary We iterate over the project "requirements" directly in a variety of places. However, it's not always the case that an input "requirement" on its own will _actually_ be part of the resolution, since we support "overrides". Historically, then, overrides haven't worked as expected for _direct_ dependencies (and we have some tests that demonstrate the current, "wrong" behavior). This is just a bug, but it's not really one that comes up in practice, since it's rare to apply an override to your _own_ dependency. However, we're now considering expanding the lookahead concept to include local transitive dependencies. In this case, it's more and more important that overrides and constraints are handled consistently. This PR modifies all the locations in which we iterate over requirements directly, and modifies them to respect overrides (and constraints, where necessary).		2024-03-31 14:03:49 -04:00
..
src	Respect overrides in all direct-dependency iterators (#2742)	2024-03-31 14:03:49 -04:00
Cargo.toml	Use distinct Constraints and Overrides types more widely (#2741)	2024-03-31 13:46:37 -04:00