]> Cypherpunks repositories - gostls13.git/commit
cmd/compile: use a non-fragile test for "does f contain closure c?"
authorDavid Chase <drchase@google.com>
Fri, 25 Oct 2024 18:04:22 +0000 (14:04 -0400)
committerDavid Chase <drchase@google.com>
Sat, 26 Oct 2024 02:44:00 +0000 (02:44 +0000)
commit889abb17e125bb0f5d8de61bb80ef15fbe2a130d
treea19740f1dba8c916fc011a95ee429aa865375579
parent6dc99aa7eb26e7cf9af0d2cab74c5027fec8cde2
cmd/compile: use a non-fragile test for "does f contain closure c?"

The old test relied on naming conventions.  The new test
uses an explicit parent pointer chain initialized when the
closures are created (in the same place that the names
used in the older fragile test were assigned).

Fixes #70035.

Change-Id: Ie834103c7096e4505faaff3bed1fc6e918a21211
Reviewed-on: https://go-review.googlesource.com/c/go/+/622656
Reviewed-by: Keith Randall <khr@golang.org>
Reviewed-by: Keith Randall <khr@google.com>
Reviewed-by: Cuong Manh Le <cuong.manhle.vn@gmail.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
src/cmd/compile/internal/escape/solve.go
src/cmd/compile/internal/ir/func.go
src/cmd/compile/internal/ir/sizeof_test.go
src/cmd/compile/internal/rangefunc/rangefunc_test.go