Safer env for recursives + variable identity. #56
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.
The change with the "@" characters is a bit of paranoia, as different pairs of types may concatenate to the same string ("aa".."b" and "a".."ab") and this may cause evaluation errors in the future.
Note the change in
subtype_variable
for when the two entries have equal names. This is the important one. Please verify if this is semantically correct. Here it seems to solve #55, but I don't know if that's enough. Maybe this is just hiding the real problem.I don't know if I'm understanding correctly the way the structural type system is supposed to work. With this patch, the code in #55 gives no errors, but the variant below still fails: