2 - Not sure if the {{ return }} command is legit without return variable. And in any case {{ return $myvar }} is evaluate ONCE in the partial and is NOT affected by the go template logic.
No-no, nil in brackets was my gotcha of yesterday
Thanks for the link, it was quite an entertaining reading while walking in the local forest. It actually answers my question.
I have seen this “return statement” confusion before – the short story, again, I implemented this crude version of “return” in 2 hours. Doing it the right way would have taken me hundreds, at least.
Yes, I’ve read this heated discussion thread, and I don’t want to re-ignite it. You are right: while less than perfect, it is far more useful than nothing. I’m not paying anything for the software, and use it while enjoying very efficient support.
One suggestion, though: since this behavior is rather unusual, the documentation should scream about it, and it won’t take long to accomplish. I might volunteer for the task once I’m done with my theme. Until then – thanks for the feature.