Skip to content
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

Move (some) not-yet-implemented errors to later stages #461

Open
sbillig opened this issue Jun 21, 2021 · 0 comments
Open

Move (some) not-yet-implemented errors to later stages #461

sbillig opened this issue Jun 21, 2021 · 0 comments

Comments

@sbillig
Copy link
Collaborator

sbillig commented Jun 21, 2021

What is wrong?

The analyzer rejects code that uses features that aren't yet implemented in some stage of the compiler pipeline. In some cases, it would be convenient to implement and test support for those features in the earlier stages (parser/analyzer/lowerer) before they're supported in the late stages. Eg the tests for lowering of nested tuples (tuples in tuples, or tuples in arrays) (#459) can't analyze the lowered AST because the lowered code uses nested structs.

How can it be fixed

Let the late stages emit their not-yet-implemented errors where appropriate.

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

No branches or pull requests

1 participant