text/template: "call" function has become too picky about function types #17714
Labels
FrozenDueToAge
NeedsDecision
Feedback is required from experts, contributors, and/or the community before a change can be made.
Milestone
The template packages have become pickier about the types of the functions they invoke with
call
, and less willing to peek into interface{} values to see if they contain a function. I encountered this in an application that works well with Go 1.7 but which is currently broken with Go tip.What version of Go are you using (
go version
)?What operating system and processor architecture are you using (
go env
)?What did you do?
https://play.golang.org/p/F0PUZ5thdZ
What did you expect to see?
I expected the script to produce no output, with exit status 0
What did you see instead?
This appears to have been broken by 5378dd7, https://golang.org/cl/31462
The text was updated successfully, but these errors were encountered: