aboutsummaryrefslogtreecommitdiff
path: root/test/codegen
diff options
context:
space:
mode:
authorDmitri Shuralyov <dmitshur@golang.org>2022-05-14 22:45:05 -0400
committerGopher Robot <gobot@golang.org>2023-01-19 22:42:34 +0000
commit47a0d467161c10f80bc3fcf7b0385b80d1194c7a (patch)
tree07c9ad922004cdc130af9e80da5c4328ef01171d /test/codegen
parent213495a4a67c318a1fab6e76093e6690c2141c0e (diff)
downloadgo-47a0d467161c10f80bc3fcf7b0385b80d1194c7a.tar.xz
cmd/compile/internal/ssa: generate code via a //go:generate directive
The standard way to generate code in a Go package is via //go:generate directives, which are invoked by the developer explicitly running: go generate import/path/of/said/package Switch to using that approach here. This way, developers don't need to learn and remember a custom way that each particular Go package may choose to implement its code generation. It also enables conveniences such as 'go generate -n' to discover how code is generated without running anything (this works on all packages that rely on //go:generate directives), being able to generate multiple packages at once and from any directory, and so on. Change-Id: I0e5b6a1edeff670a8e588befeef0c445613803c7 Reviewed-on: https://go-review.googlesource.com/c/go/+/460135 Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Reviewed-by: Keith Randall <khr@google.com> Auto-Submit: Dmitri Shuralyov <dmitshur@golang.org> Run-TryBot: Dmitri Shuralyov <dmitshur@golang.org> TryBot-Result: Gopher Robot <gobot@golang.org> Reviewed-by: Keith Randall <khr@golang.org>
Diffstat (limited to 'test/codegen')
0 files changed, 0 insertions, 0 deletions