-
Notifications
You must be signed in to change notification settings - Fork 12.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Remove experimental chalk option #69247
Conversation
r? @cramertj (rust_highfive has picked a reviewer for you, use r? to override) |
FWIW, I've gotten (locally) the Chalk-related code updated to the latest Chalk master (with some modifications that'll get PRed soon). It compiles but |
Just for good measure, I suppose I should cc @rust-lang/wg-traits |
☔ The latest upstream changes (presumably #69242) made this pull request unmergeable. Please resolve the merge conflicts. |
✌️ @CAD97 can now approve this pull request |
Rebased. If only GitHub actually had a way to show just the conflict resolution of the rebase... @bors r=nikomatsakis |
📌 Commit 02b872ed51d74eb48b07e5dd7b15d51636bf7e76 has been approved by |
@bors r- Tidy failures crept into the rebase; investigating |
@bors: r=nikomatsakis I missed a trailing newline, that's it. |
📌 Commit b3777c9 has been approved by |
☀️ Test successful - checks-azure |
Removed in rust-lang#69247 while this PR was waiting to merge.
As suggested by @nikomatsakis here.
The current version of chalk used by the experimental
-Zchalk
flag is v0.9.0, which is over a year old. Since v0.9.0, chalk has seen a lot of further development, and the intent is to eventually upgrade rustc to use a more recent chalk.However, it will take a decent chunk of effort to upgrade the current experimental chalk support, and it is currently blocking at least some PRs due to chalk:0.9.0's use of unstable features. So for the interim until the next chalk release and experimental rustc integration, we remove the chalk-specific code from rustc.