Skip to content
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

Upgrade Chalk #6597

Merged
merged 1 commit into from
Dec 7, 2020
Merged

Upgrade Chalk #6597

merged 1 commit into from
Dec 7, 2020

Conversation

flodiebold
Copy link
Member

Also make overflow depth and max type size configurable through env variables. This can be helpful at least for debugging.

Tests currently fail because of rust-lang/chalk#656, so we'll need to wait for the next update to merge this.

@jackh726
Copy link
Member

@flodiebold that PR is merged; feel free to do a release for Chalk if you want to merge this before the release next weekend

@kjeremy
Copy link
Contributor

kjeremy commented Nov 30, 2020

@flodiebold Chalk 41 has been released which contains your fix.

@flodiebold
Copy link
Member Author

@kjeremy Yeah, but it also causes #6628, so I think we have to wait a bit longer...

@kjeremy
Copy link
Contributor

kjeremy commented Nov 30, 2020

😢

@cynecx
Copy link
Contributor

cynecx commented Dec 6, 2020

rust-lang/chalk#658 has been closed, so #6628 should work now?

@flodiebold
Copy link
Member Author

It should, but there's no new Chalk release yet.

@jackh726
Copy link
Member

jackh726 commented Dec 6, 2020

@flodiebold 0.43 has been released.

Also make overflow depth and max type size configurable through env variables.
This can be helpful at least for debugging.

Fixes rust-lang#6628.
@flodiebold
Copy link
Member Author

bors r+

@bors
Copy link
Contributor

bors bot commented Dec 7, 2020

@bors bors bot merged commit 403ed48 into rust-lang:master Dec 7, 2020
@flodiebold flodiebold deleted the chalk-39 branch December 7, 2020 10:59
@lnicola
Copy link
Member

lnicola commented Dec 10, 2020

Looks like this brought a nice perf improvement (the visible drop towards the right), cc @jackh726:

image

image

@jackh726
Copy link
Member

@lnicola wow! That's impressive. I didn't even think about it, but that's probably the fold by value change. I'm actually really shocked, because when the same thing was implemented in rustc, IIRC there wasn't a huge perf win.

@matklad
Copy link
Member

matklad commented Dec 10, 2020

While we are at this exciting topic, has anyone by any chance looked at enabling instruction counts on github actions? SO that we could have timings much more precise than wall-clock time.

@lnicola
Copy link
Member

lnicola commented Dec 10, 2020

Last time we tried, it didn't seem to work, probably because of security limitations. And on the topic of metrics, we're no longer reporting memory usage since #5581.

@flodiebold
Copy link
Member Author

I think rust-lang/chalk#638 might also have played a role; I think/hope it's preventing us from enumerating all impls for a trait in a lot of cases where we previously would.

@jackh726
Copy link
Member

I think rust-lang/chalk#638 might also have played a role; I think/hope it's preventing us from enumerating all impls for a trait in a lot of cases where we previously would.

Ah. That seems a bit more likely to me.

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.

6 participants