mirror of
https://github.com/golang/go.git
synced 2025-12-08 06:10:04 +00:00
cmd/compile: workaround inlining of closures with range statements
ORANGE is still not inlineable now. This CL is correct only when the range statement is statically dead, and thus not counted during the inline budget check. If we support range statements in inlining closures in the future, may require additional processing. Fixes #48033. Change-Id: I28f5755c28cfa27e41daef9eff2ae332059909bb Reviewed-on: https://go-review.googlesource.com/c/go/+/345436 Trust: Cherry Mui <cherryyz@google.com> Reviewed-by: Keith Randall <khr@golang.org>
This commit is contained in:
parent
6705191e02
commit
08e2519ded
2 changed files with 42 additions and 0 deletions
|
|
@ -1061,6 +1061,8 @@ func (subst *inlsubst) clovar(n *ir.Name) *ir.Name {
|
|||
m.Defn = &subst.defnMarker
|
||||
case *ir.TypeSwitchGuard:
|
||||
// TODO(mdempsky): Set m.Defn properly. See discussion on #45743.
|
||||
case *ir.RangeStmt:
|
||||
// TODO: Set m.Defn properly if we support inlining range statement in the future.
|
||||
default:
|
||||
base.FatalfAt(n.Pos(), "unexpected Defn: %+v", defn)
|
||||
}
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue