Skip to content

Known limitations of static error detection #2

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

Open
5 tasks
alastairreid opened this issue Dec 19, 2024 · 0 comments
Open
5 tasks

Known limitations of static error detection #2

alastairreid opened this issue Dec 19, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@alastairreid
Copy link

alastairreid commented Dec 19, 2024

We know about the following limitations in static error detection

Typechecking

  • Duplicate definitions (of types, variables, functions, record fields, etc.) are not always detected
  • Parser is not always detecting ambiguous precedence
  • Uninitialized local variables are not being detected / reported
  • Unused local variables should generate a warning message
  • Procedures (functions with no return type) should report an error for "return ;"
@alastairreid alastairreid added the bug Something isn't working label Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant