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
Type-check aliasing in separate pass #1977
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
One piece of functionality is missing: all variables are now reported as unused, because the alias checking machinery did double duty as a usage checker. That'll need its own mechanism now. |
razetime
pushed a commit
to razetime/futhark
that referenced
this pull request
Jul 16, 2023
This significantly simplifies the type checker, and also fixes known (and future) bugs related to tracking aliases of an incompletely typed term. This also allows us to provide better error messages, although it's possible that they are currently slightly worse, as the aliasing checking does not use the "context" mechanism of the term-level type checker. The AST itself is simplified because it no longer has to embed alias information (which wasn't correct anyway, and was not actually used). There is one user-visible change: lambdas that must return an alias-free result will now require a return type annotation. We may loosen this in the future, but it is a very rare case in practice. Closes diku-dk#1872.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This significantly simplifies the type checker, and also fixes known
(and future) bugs related to tracking aliases of an incompletely typed
term.
This also allows us to provide better error messages, although it's
possible that they are currently slightly worse, as the aliasing
checking does not use the "context" mechanism of the term-level type
checker.
The AST itself is simplified because it no longer has to embed alias
information (which wasn't correct anyway, and was not actually used).
There is one user-visible change: lambdas that must return an
alias-free result will now require a return type annotation. We may
loosen this in the future, but it is a very rare case in practice.
Closes #1872.