-
Notifications
You must be signed in to change notification settings - Fork 13.4k
StableMIR: Prepare for refactoring #139319
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Conversation
These commits modify the If this was unintentional then you should revert the changes before this PR is merged. This PR changes Stable MIR |
This comment has been minimized.
This comment has been minimized.
c9ca224
to
c8c7d1f
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please r=me once you address the comments.
☔ The latest upstream changes (presumably #139396) made this pull request unmergeable. Please resolve the merge conflicts. |
@bors r=celinval |
…iaskrgr Rollup of 5 pull requests Successful merges: - rust-lang#136877 (Fix missing const for inherent pointer `replace` methods) - rust-lang#138797 (Fix `ProvenVia` for global where clauses) - rust-lang#139121 (Rename internal module from `statik` to `no_threads`) - rust-lang#139319 (StableMIR: Prepare for refactoring) - rust-lang#139404 (Small smir cleanup) r? `@ghost` `@rustbot` modify labels: rollup
Rollup merge of rust-lang#139319 - makai410:refactor, r=celinval StableMIR: Prepare for refactoring Temporarily make `stable_mir` "parasitic" on the `rustc_smir` crate. It aims to resolve the circular dependency that would arise if we directly invert the dependency order between `rustc_smir` and `stable_mir`. Once the refactoring is complete (`rustc_smir` does not depend on `stable_mir`), we will migrate it back to the `stable_mir` crate. See more details: [here](https://hackmd.io/jBRkZLqAQL2EVgwIIeNMHg).
Temporarily make
stable_mir
"parasitic" on therustc_smir
crate.It aims to resolve the circular dependency that would arise if we directly invert the dependency order between
rustc_smir
andstable_mir
.Once the refactoring is complete (
rustc_smir
does not depend onstable_mir
), we will migrate it back to thestable_mir
crate. See more details: here.