Optimisation: avoid emitting type tests for verify bounds that always hold#152579
Open
amandasystems wants to merge 1 commit intorust-lang:mainfrom
Open
Optimisation: avoid emitting type tests for verify bounds that always hold#152579amandasystems wants to merge 1 commit intorust-lang:mainfrom
amandasystems wants to merge 1 commit intorust-lang:mainfrom
Conversation
… hold This makes more sense than you'd imagine since empty `All` bounds which always hold is relatively common.
d55cf4c to
6b612a0
Compare
lcnr
reviewed
Feb 13, 2026
| if bound.must_hold() { | ||
| debug!("Bound {bound:?} always holds; emitting no type test."); | ||
| return; | ||
| } |
Contributor
There was a problem hiding this comment.
this feels potentially quite surprising to me.
can we instead avoid constructing these verify bounds in the first place?
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.
This makes more sense than you'd imagine since empty
Allbounds which always hold are is a relatively common use of them and a bound that always holds produces no promoted constraints.r? @lcnr