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
This relate's in part to issue #7445.
Currently Execute is documented as:
Execute applies a parsed template to the specified data object, and writes the output to
wr.
I believe it should say that if a write error is encountered, the remainder of the
template will not be executed.
I discovered this behaviour when serving templates over http, ranging over a channel,
which was populated by a goroutine. If the network connection prematurely closed, the
goroutine would lock up/memory leak.
This might also be worth a mention with the range command when dealing with channels.
The text was updated successfully, but these errors were encountered:
Execute applies a parsed template to the specified data object, and
writes the output to wr. If an error occurs executing the template or
writing its output, ***execution stops***...
We can't enumerate every possible meaning of stop.
That second sentence was added by https://golang.org/cl/94640043 (closing issue
7445) 45 hours ago, long after this bug was filed. But happy to see the sentence there,
so yes it now is working as intended :-)
by krolaw:
The text was updated successfully, but these errors were encountered: