How can I override a template block with an empty template?

Using text/html I define a block in my base template, containing default content. In some situations I would like this block to be empty, so I thought I could just re-define its name and make it contain nothing like:

{{ block "something" . }}
    <h1>Default content</h1>
{{ end }}

// later in a place that does not want "something" ...
{{ define "something" }}{{ end }}

Somehow Go seems to think that this definition is "Zero" and will still render the default content unless I put any non-whitespace content into the definition.

I found this issue on the Golang repo which describes the very same thing nicely in a Playground example:

package main

import (
	"fmt"
	"os"
	"runtime"
	"text/template"
)

func main() {

	fmt.Printf("Version: %q\n", runtime.Version())

	t, err := template.New("master").Parse(`{{block "area51" .}}Original Content{{end}}`)
	if err != nil {
		panic(err)
	}
	t, err = t.New("other_template").Parse(`{{define "area51"}}{{end}}`)
	if err != nil {
		panic(err)
	}

	fmt.Printf("Output:\n")
	if err := t.ExecuteTemplate(os.Stdout, "master", nil); err != nil {
		panic(err)
	}

	fmt.Printf("\n")

}

Weirdly, the issue mention it is fixed (and landed in 1.8.1 if I understand it correctly), but it does not work for me, neither with 1.8.1+ nor 1.9.

Is this a bug in Golang or is the approach flawed? Do I need to do anything differently in order to re-define the block so that it renders empty?

This is the expected behavior. This is documented at Template.Parse():

> Templates can be redefined in successive calls to Parse, before the first use of Execute on t or any associated template. A template definition with a body containing only white space and comments is considered empty and will not replace an existing template's body. This allows using Parse to add new named template definitions without overwriting the main template body.

So you can't "erase" an already defined template (you can't replace its content to be empty).

If you "conditionally" need it, then use an {{if}} action to decide if the template is to be called. Alternatively you may put an {{if}} inside the template, and the template itself may choose not to render anything. In this case you have to make sure to pass the proper argument that controls what the template will render.

P.S. If you're working with HTML templates, you should always use html/template instead of text/template, as the former provides the same interface as package text/template but also provides contextual escaping to generate HTML output safe against code injection.