It may be more flexible to have a cfg.Format function that takes an enum where Graphviz and the [default] (*CFG).Format are the initial options. This is also debatably overkill.

It may be more flexible to have a cfg.Format function that takes an enum where Graphviz and the [default] (*CFG).Format are the initial options.

CFG already has a Format method that doesn't take an enum.

Let's call it dot to match pprof's -dot flag. Otherwise seems fine.

This proposal has been added to the active column of the proposals project
and will now be reviewed at the weekly proposal review meetings.
— rsc for the proposal review group

Based on the discussion above, this proposal seems like a likely accept.
— rsc for the proposal review group

The proposal is to add:

// Dot returns the control-flow graph in the [Dot graph description language].
// Use a command such as 'dot -Tsvg' to render it in a form viewable in a browser.
// This method is provided as a debugging aid; the details of the
// output are unspecified and may change. 
//
// [Dot graph description language]: ​​https://en.wikipedia.org/wiki/DOT_(graph_description_language)
func (g *CFG) Dot(fset *token.FileSet) string

No change in consensus, so accepted. 🎉
This issue now tracks the work of implementing the proposal.
— rsc for the proposal review group

The proposal is to add:

// Dot returns the control-flow graph in the [Dot graph description language].
// Use a command such as 'dot -Tsvg' to render it in a form viewable in a browser.
// This method is provided as a debugging aid; the details of the
// output are unspecified and may change. 
//
// [Dot graph description language]: ​​https://en.wikipedia.org/wiki/DOT_(graph_description_language)
func (g *CFG) Dot(fset *token.FileSet) string

Change https://go.dev/cl/572016 mentions this issue: go/cfg: publish (*CFG).Dot method