[red-knot] Merge the semantic and module-resolver crates #12751
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR merges the
red_knot_python_semantic
andred_knot_module_resolver
crates. Since this involves moving quite a few files, this PR only merges the two crates, and doesn't do anything else. The module resolver becomes a self-contained submodule ofred_knot_python_semantic
, except formodule_name.rs
, which becomes a top-level submodule ofred_knot_python_semantic
.(None of the vendored typeshed files have changed in any way, only moved. You should be able to scroll past them when looking at the diff.)
The motivation for this is that it should make it easier to validate settings for search paths eagerly, outside of Salsa.
Test Plan
cargo test