Skip to content

Fix substitution into record projection by type #1012

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Jun 19, 2019
Merged

Conversation

Gabriella439
Copy link
Collaborator

Fixes #1009

The subst/shift/subExpressions functions did not correctly
reflect the recent change to support projection by type

Fixes #1009

The `subst`/`shift`/`subExpressions` functions did not correctly
reflect the recent change to support projection by type
@quasicomputational
Copy link
Collaborator

Change looks good to fix the proximal problem, but I'm still concerned by how the testsuite wasn't able to catch it.

I guess the test code isn't using the same code-path as the production code somehow.

@Gabriella439
Copy link
Collaborator Author

Gabriella439 commented Jun 18, 2019

@quasicomputational: It's because the normalization test suite wasn't type-checking the code. The (slower) type-checking code uses the subst/shift functions whereas the faster normalization code does not.

The absence of type-checking is the difference between the test code path and the production code path. The reason the test code is not type-checking is because of the unit tests (which are not well-typed since they are full of unbound variables).

@Gabriella439 Gabriella439 merged commit 5c93429 into master Jun 19, 2019
@Gabriella439 Gabriella439 deleted the gabriel/1009 branch June 19, 2019 01:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Record projection by expression doesn't allow the expression to be a variable
2 participants