-
Notifications
You must be signed in to change notification settings - Fork 14
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
No error handling for Go #9
Comments
That's right, a middleware that implements Go-style error checks was in the works, however currently that's not implemented. As a whole this projects is currently on hold: I am currently focused on my job and different projects. I'll probably finish a more stable new version if there is any interest in it. (The people interested in this project had vastly different usecases/wishes for its functionality so I decided to wait for a compelling usecase) |
Fair enough. I'm certainly interested in this project. I'm contributing to Grumpy (a Python runtime in Go) which aims to support most of Python2.7 in all its dynamic glory, but it does so by compiling everything into a Go |
That's a very nice idea, but you're right, it's outside the scope of this project. Grumpy is pretty interesting, I wonder if somebody is building a Ruby runtime on Go too. |
Compiling the following program to Go produces no error handling logic:
When we
go run foo.go "not_an_int"
, the program prints0
and exists successfully. When wepython3 foo.py "not_an_int"
, we see:The text was updated successfully, but these errors were encountered: