Don't fire OPAQUE_HIDDEN_INFERRED_BOUND
on sized return of AFIT
#120360
+30
−1
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.
Conceptually, we should probably not fire
OPAQUE_HIDDEN_INFERRED_BOUND
for methods like:Even though we technically cannot prove that
Self: Sized
, which is one of the item bounds of theOutput
type in the-> impl Future<Output = Sized>
from the async desugaring.This is somewhat justifiable along the same lines as how we allow regular methods to return
-> Self
even thoughSelf
isn't sized.Fixes #113538
(side-note: some days i wonder if we should just remove the
OPAQUE_HIDDEN_INFERRED_BOUND
lint... it does make me sad that we have non-well-formed types in signatures, though.)