-
Notifications
You must be signed in to change notification settings - Fork 34
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
fail statement #677
Comments
This sounds more like |
I'm very doubtful of adding a new keyword just for this. Why not make it a toplevel function of Also it reminds me a lot of the |
Definite return checking now special-cases |
Also relevant for definite assignment. Done now. |
Should we introduce a
fail
statement, that means, approximately,assert (false)
? I hate adding a whole new keyword just for this, but it's conceptually useful.At the very least we should make definite assignment / definite return analysis treat
assert (false)
as a special case.The text was updated successfully, but these errors were encountered: