Improve inference of Ghost when erased #905
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.
See: verus-lang/verus#875
This improves the type inference of
gh!
when dealing with erased code.Previously, it was required to always annotate
gh
bindings if you wanted the erased code to work. This was because when thegh
code is erased, type inference is missing information to determine a concrete type andrustc
will reject the code as ambiguous.For example, the following failed to compile with
rustc
previously:This PR fixes it by exploiting the coercion from
!
to any type in Rust, so that when erased, we will 'default' toGhost<!>
while remaining capable to unify with any possible type annotation that was provided in a binding.this was found in collaboration with @utaal