Arity check types and functions (->) #2049
Merged
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 pr fixes the following:
This example causes the compiler to crash with "implicitness mismatch".
The reason is that
id
expects an implicit argument but findsBool
, which is explicit. The arity checker was not inserting any hole because it was ignoring the whole type. Moreover the aritychecker was never checking->
types as we never expected tohave to insert holes in
->
types (since the only fragment of defined functions that we accept in types are those which do not have implicit arguments).We now properly arity check all types and process the function type
->
correctly.