-
Notifications
You must be signed in to change notification settings - Fork 18k
runtime: out-of-memory error is inscrutable #594
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
Labels
Milestone
Comments
I'd like to see a further enhancement to make(): I'd like it to report failure other than with a runtime error. This needn't break backward compatibility other than very minorly, e.g.: var buf []byte var ok os.Error buf, ok = make([]byte, ...) // return with ok != nil on failure buf = make([]byte, ...) // runtime error as currently implemented Providing the make() is presumed to provide two values any time it is used in tuple assignment, existing code like the following would at least get an "assignment count mismatch" compile time error: var buf []byte var s string buf, s = make([]byte, ...), "fubar" file.go: assignment count mismatch: 3 = 2 Or maybe it's not too late an incompatible change; the language still seems at least somewhat in flux. |
Issue #620 has been merged into this issue. |
Owner changed to builder@golang.org. |
This issue was closed.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The text was updated successfully, but these errors were encountered: