-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Have never
implicitly return from its location.
#12883
Labels
Duplicate
An existing issue was already created
Comments
this is a duplicate of #12825. the issue is that the compiler does things in phases. when it knows about the control flow, it does not know about types. so it is an implementation limitation, both issues have the same limitation. it is not an issue of how to handle |
Oh. So it would be much more difficult to accomplish than I initially
anticipated. I didn't realize that.
On Tue, Dec 13, 2016, 12:48 Mohamed Hegazy <notifications@github.com> wrote:
this is a duplicate of #12825
<#12825>. the issue is that
the compiler does things in phases.
So I'm guessing past phases have no way of communicating to future phases
any node-specific data? How difficult would that be?
when it knows about the control flow, it does not know about types. so it
is an implementation limitation, both issues have the same limitation. it
is not an issue of how to handle never when found.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12883 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AERrBCIQLmrLNvVO3xkV2C3Ci1X7zbTqks5rHtqKgaJpZM4LL3Lr>
.
|
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
This would fix #12825, and pave the way for another suggestion to fix #8655. I'll link the proposed fix's issue here after I submit it.
The text was updated successfully, but these errors were encountered: