Skip to content

Conversation

@davidtwco
Copy link
Member

@davidtwco davidtwco commented Oct 28, 2025

Blog post for rust-lang/compiler-team#938 once that MCP completes

Rendered

@Noratrieb
Copy link
Member

leaving comments would have been easier if you used semantic line breaks instead of hard wrapping at a column count :)

@davidtwco davidtwco force-pushed the v0-mangling-on-nightly branch 2 times, most recently from 0836ea0 to 0cab632 Compare November 3, 2025 15:29
If that happens, you can use the legacy mangling scheme with
the `-Csymbol-mangling-version=legacy -Zunstable-options` flag.
Using the legacy mangling scheme requires nightly, it is not intended
to be stabilised so that support can eventually be removed. Either by
Copy link
Member

Choose a reason for hiding this comment

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

I still think we should stabilize it with the intent to deprecate and remove (/make it a no-op) it eventually just to ease the transition for people when it hits stable.
imo making it a no-op after stabilizing is not any more breaking than changing the default in the first place

Copy link
Member Author

Choose a reason for hiding this comment

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

I'm open to doing this but haven't included it in the blog post or patch yet, will ask in the MCP thread and see what others in the team think

Copy link
Contributor

@teor2345 teor2345 left a comment

Choose a reason for hiding this comment

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

I think the usage instructions could be a bit clearer

@davidtwco davidtwco force-pushed the v0-mangling-on-nightly branch from 0cab632 to ee8ae66 Compare November 10, 2025 12:09
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.

9 participants