-
Notifications
You must be signed in to change notification settings - Fork 43
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
ng/eval: defer outside a function scope #210
Comments
sbinet
added a commit
to sbinet-gonum/ng
that referenced
this issue
Jan 16, 2018
sbinet
added a commit
to sbinet-gonum/ng
that referenced
this issue
Jan 17, 2018
sbinet
added a commit
to sbinet-gonum/ng
that referenced
this issue
Mar 9, 2018
sbinet
added a commit
to sbinet-gonum/ng
that referenced
this issue
Mar 9, 2018
sbinet
added a commit
to sbinet-gonum/ng
that referenced
this issue
Mar 9, 2018
sbinet
added a commit
that referenced
this issue
Mar 9, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
right now, when doing this (in Jupyter or directly in
ng
) one gets:as mentioned here we should probably put all the top-level code insider a "fake"
"ng-main"
function scope so we get a defer-context to hang all the top-leveldefer
s on to.what do you think @crawshaw ?
would this break something somewhere?
(
go test ./...
didn't complain)The text was updated successfully, but these errors were encountered: