Adding closure resolution - Part 1 #8
Draft
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.
Add closure expression resolution to transform Raw.ClosureExpr into
Ast.ClosureExpr with fully resolved types and expressions.
New Methods in ExprResolver.dfy
ResolveClosureExpr: Main entry point for closure resolution
ResolveClosureBindingWithWF: Resolves a single closure binding
ResolveClosurePropertyWithWF: Resolves a single closure property
API Changes
Added ers.Valid() precondition to:
This is required to prove b3.IsType() for resolved types using the
equivalence: b3.IsType(t) <==> t in BuiltInTypes || t in typeMap
Design Fix in RawAst.dfy
Updated Raw.ClosureProperty.WellFormed signature to include resultVar
Extended property scope to include:
Previously only included outer scope + binding params, which was
insufficient for properties that reference result var or binding names.