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.
In #492, I decided to use
Free
vars for the type-level variables bound in the signature andBound
variables for those bound in an inner binder. After trying to implement the next PR that requires some non-trivial binder handling, this turned out to be a pain.In this PR, I use
Bound
variables everywhere inside charon. I restore the "Free
for signature-bound vars" usage in a micro-pass done at the end.There is still one different with what was done before this PR:
ImplElem::Ty
contains a bbinder that used to be refered to usingFree
variables ad now uses `Boundè variables to avoid substitution mistakes.