Fix bug conversions of function returning function failed #82398
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.
Description
resolves #82397
regression of #78377
Since the new condition doesn’t handle the case where both
lhs
andrhs
have the same curry levels, conversions of function-returning functions are incorrectly repaired byrepairByInsertingExplicitCall
. It should be resolved byValueToOptionalConversion
by returning false inrepairByInsertingExplicitCall
.Solution
improve guard condition at
repairByInsertingExplicitCall
, specially: check curry levels oflhs
andrhs
. iflhs
doesn't have more curry levels thanrhs
, it shouldn't be repaired by InsertingExplicitCall.note that since the existing logic (
!resultType->is<FunctionType>()
) is designed to ensure thatlhs
has 2 (or more) curry levels andrhs
has 1 (or more) curry level, The new guard logic (
lhs.curryLevels <= rhs.curryLevels
) include this existing logic.