]> Cypherpunks repositories - gostls13.git/commit
[release-branch.go1.23] cmd/compile: use a non-fragile test for "does f contain closu...
authorDavid Chase <drchase@google.com>
Fri, 25 Oct 2024 18:04:22 +0000 (14:04 -0400)
committerGopher Robot <gobot@golang.org>
Tue, 19 Nov 2024 17:52:28 +0000 (17:52 +0000)
commit3726f07c4650d266b58b828432b3f8dab6d553d7
treeb55947e7e6cf84138c7703c21ba37c97d914b2c1
parentc390a1c22e8951263e6c01346a4281d604b25062
[release-branch.go1.23] 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 #70198.

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>
Reviewed-on: https://go-review.googlesource.com/c/go/+/625535
Auto-Submit: Dmitri Shuralyov <dmitshur@google.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