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.

Sign up for GitHub

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

Jump to bottom

Formal arguments of undefined type can cause a cascade of spurious errors #1075

Closed
degory opened this issue Feb 20, 2024 · 0 comments · Fixed by #1076
Closed

Formal arguments of undefined type can cause a cascade of spurious errors #1075

degory opened this issue Feb 20, 2024 · 0 comments · Fixed by #1076
Labels
bug

Comments

@degory
Copy link
Owner

degory commented Feb 20, 2024

Declaring functions or methods with formal arguments that are syntactically well formed but that have undefined types can cause a huge cascade of spurious unrelated errors.

The issue is caused by null reference exceptions in METHOD_OVERRIDE_CLASS. This either needs to gracefully handle null argument types, or, preferably, the source of the nulls needs to be fixed to produce Type.ERROR instead
@degory degory added the bug label Feb 20, 2024
degory added a commit that referenced this issue Feb 20, 2024
@degory
Fix error cascade when undefined type used as formal argument
73c5194 
Bugs fixed:
- Formal arguments of undefined type can case a cascade of spurious errors (closes #1075)

Technical:
- Bump compiler tool to latest
- Bump integration test runner tool to latest
- Bump runtime library to latest
- Replace instances of deprecated `| .has(...)` with `| .any(...)`
@degory degory mentioned this issue Feb 20, 2024
Merged
degory added a commit that referenced this issue Feb 20, 2024
@degory
Fix error cascade when undefined type used as formal argument (#1076)
8c9df61 
Bugs fixed:
- Formal arguments of undefined type can case a cascade of spurious errors (closes #1075)

Technical:
- Bump compiler tool to latest
- Bump integration test runner tool to latest
- Bump runtime library to latest
- Replace instances of deprecated `| .has(...)` with `| .any(...)`
@degory degory changed the title Formal arguments of undefined type can case a cascade of spurious errors Formal arguments of undefined type can cause a cascade of spurious errors Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
ghūl programming language - stable release
Status: Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix error cascade when undefined type used as formal argument degory/ghul
1 participant
@degory