feat: Allow calling higher-order functions with closures #2335
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
Problem*
Initial work towards #2334
Summary*
This is work towards allowing higher-order functions to be called with closure arguments. The bulk of the work will be done in the monomorphizer in the next PRs, this is a prerequisite that allows higher-order functions called with closures to pass type-checking.
A method called
try_unify_allow_incompat_lambdas
is added that is used instead oftry_unify
for function arguments. The only difference between it andtry_unify
is that it doesn't check function type capture groups.This also fixes some comments that reference the removed
make_subtype_of
functionsDocumentation
This PR requires documentation updates when merged.
Additional Context
PR Checklist*
cargo fmt
on default settings.