-
Notifications
You must be signed in to change notification settings - Fork 569
bug: nil variable definition causes compiler panic #883
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
Comments
I can't reproduce this:
Do you have a repro? |
@myitcv Check your little reproduction script, at the end you ran "gopherjs test" and got a "no test files" message. you did not actually compile the code. Try "gopherjs build -v ."
|
@paralin - doh! Thanks for spotting the obvious error. Here is the repro:
|
That's the one! |
@paralin I have a fix for this in myitcv#38 (for some reason that closed this issue which I am re-opening). Per #855 (comment) that fork will be merged back into the main repo at some point hopefully soon. |
Also to note, per @paralin's observation above, there is a difference in behaviour between
|
Add the following line to the bottom of a Go file:
This causes a Go compiler error.
Full compiler output and reproduce here:
https://gist.github.com/paralin/ef8a9b472baa6ecedfc708679a0f308c
The text was updated successfully, but these errors were encountered: