Skip to content

Conversation

@celinval
Copy link
Contributor

I am updating the documents to avoid using StableMIR and to use rustc_public as the crate name. Let me know if that makes sense.

@makai410 / @oli-obk

Rename from "Stable MIR" to better reflect the goal of providing
SemVer compliant APIs rather than completely stable APIs.
Copy link
Contributor

@makai410 makai410 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Update the description to reflect the recent refactoring that moves conversion logic to `rustc_public`.
@celinval celinval merged commit 809abee into rust-lang:main Nov 20, 2025
3 of 8 checks passed
makai410 pushed a commit to makai410/rustc_public that referenced this pull request Dec 1, 2025
* Rename project to "Rustc Librarification"

Rename from "Stable MIR" to better reflect the goal of providing
SemVer compliant APIs rather than completely stable APIs.

* Update README.md

Update the description to reflect the recent refactoring that moves conversion logic to `rustc_public`.
makai410 pushed a commit to makai410/rustc_public that referenced this pull request Dec 2, 2025
* Rename project to "Rustc Librarification"

Rename from "Stable MIR" to better reflect the goal of providing
SemVer compliant APIs rather than completely stable APIs.

* Update README.md

Update the description to reflect the recent refactoring that moves conversion logic to `rustc_public`.
makai410 pushed a commit to makai410/rustc_public that referenced this pull request Dec 2, 2025
* Rename project to "Rustc Librarification"

Rename from "Stable MIR" to better reflect the goal of providing
SemVer compliant APIs rather than completely stable APIs.

* Update README.md

Update the description to reflect the recent refactoring that moves conversion logic to `rustc_public`.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants