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

Fix performance regression for with expressions #2112

Merged
merged 2 commits into from
Dec 10, 2020
Merged

Conversation

Gabriella439
Copy link
Collaborator

Fixes: #2105

@ggilmore
Copy link

ggilmore commented Dec 8, 2020

Thank you! Would it be possible to roll this into a patch release, or should we wait for 1.38.0?

@Gabriella439
Copy link
Collaborator Author

@ggilmore: I can cut an early 1.37.1 release to get this fix out

@ggilmore
Copy link

ggilmore commented Dec 8, 2020

Awesome thank you! Also I don't know if this is the appropriate place to ask this, but is there a test that can be added to the suite that would catch this in the future? It might be tricky if the only indicator of an issue is the length of the execution time though.

@Gabriella439
Copy link
Collaborator Author

@ggilmore: Probably not. Anything that would causes tests to fail would be problematic when run on different machines (e.g. as part of Nixpkgs CI, for example)

@mergify mergify bot merged commit 9fd070f into master Dec 10, 2020
@mergify mergify bot deleted the gabriel/fix_with_speed branch December 10, 2020 06:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

possible with performance regression in 1.36.0 release
3 participants