Skip to content

fix(typechecker): show correct error for invalid sized types with using directive#932

Merged
SchoolyB merged 1 commit intobugfixes/1-7-2026from
fix/914-using-undefined-type-error
Jan 7, 2026
Merged

fix(typechecker): show correct error for invalid sized types with using directive#932
SchoolyB merged 1 commit intobugfixes/1-7-2026from
fix/914-using-undefined-type-error

Conversation

@SchoolyB
Copy link
Copy Markdown
Owner

@SchoolyB SchoolyB commented Jan 7, 2026

Summary

Changes

  • pkg/typechecker/typechecker.go: Added pattern check before using module fallback

Test plan

  • Verified i512 with using std now shows "undefined type 'i512'"
  • Verified i512 without using still shows "undefined type 'i512'"
  • All existing tests pass

…ng directive (#914)

When a `using` directive was present, undefined types like `i512` showed
"type mismatch" instead of "undefined type". Added check to detect
invalid sized type patterns (i<N>, u<N>, f<N>) and reject them before
deferring to module resolution.
@SchoolyB SchoolyB merged commit 9ba4bc0 into bugfixes/1-7-2026 Jan 7, 2026
3 checks passed
@SchoolyB SchoolyB deleted the fix/914-using-undefined-type-error branch January 7, 2026 19:34
SchoolyB added a commit that referenced this pull request Apr 3, 2026
…ng directive (#914) (#932)

When a `using` directive was present, undefined types like `i512` showed
"type mismatch" instead of "undefined type". Added check to detect
invalid sized type patterns (i<N>, u<N>, f<N>) and reject them before
deferring to module resolution.
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.

1 participant