next-solver 2025h2 #318
Open
next-solver 2025h2 #318
+87
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
it didn't change much from the h1 goal ✨ notable changes:
We've fixed all the compilation errors in our benchmarks (at least when using in-progress changes) and are now testing some of our benchmarks with the new solver by default. We have already made significant progress on fixing performance regressions, we're still slower than the old solver in the relevant benchmarks
We've done a full crater run and fixed most issues found on crater. Given our in-progress changes there is no unintended major breakage and all intended breakage in widely used crates has been fixed.
cc @compiler-errors @BoxyUwU
Rendered