Skip to content

Allow 'give up on this function scope, continue with next' errors in typeck #1504

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

Closed
marijnh opened this issue Jan 13, 2012 · 1 comment
Closed
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-type-system Area: Type system C-enhancement Category: An issue proposing an enhancement or a PR with one. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.

Comments

@marijnh
Copy link
Contributor

marijnh commented Jan 13, 2012

Currently, when the check phase comes across something it really can't type, it bails out entirely and aborts the compilation. It should not be too hard to set it up to continue typechecking other function blocks, since those are mostly separate units. (Of course, getting a function declaration wrong might result in multiple errors with the same cause, but that still seems preferable to having the compile give up completely.)

@catamorphism
Copy link
Contributor

I think that with my work on #1871, this is no longer an issue.

Kobzol pushed a commit to Kobzol/rust that referenced this issue Dec 30, 2024
bors pushed a commit to rust-lang-ci/rust that referenced this issue Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints A-type-system Area: Type system C-enhancement Category: An issue proposing an enhancement or a PR with one. E-easy Call for participation: Easy difficulty. Experience needed to fix: Not much. Good first issue.
Projects
None yet
Development

No branches or pull requests

2 participants