You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The template package is being blamed (unfairly in my opinion) for issues around SIGPIPE, but there is a fair point to be made: The template package should make it easy to distinguish errors caused by execution from errors caused by I/O. The former is a programming problem that should be fixed; the latter is just bad luck. A conscientious program (like cmd/go) could act differently in the two cases.
The text was updated successfully, but these errors were encountered:
The template package should make it easy to distinguish execution errors caused by execution from errors caused from I/O.
Not just the template package, though. I needed this distinction in net/http the other day, and I always finding myself writing little helper functions like,
See #11845
The template package is being blamed (unfairly in my opinion) for issues around SIGPIPE, but there is a fair point to be made: The template package should make it easy to distinguish errors caused by execution from errors caused by I/O. The former is a programming problem that should be fixed; the latter is just bad luck. A conscientious program (like cmd/go) could act differently in the two cases.
The text was updated successfully, but these errors were encountered: