cmd/compile: check for iteration after range func loop exit

Browse source

When this happens, panic.

This is a revised version of a check that used #next,
where this one instead uses a per-loop #exit flag,
and catches more problematic iterators.

Updates #56413.
Updates #61405.

Change-Id: I6574f754e475bb67b9236b4f6c25979089f9b629
Reviewed-on: https://go-review.googlesource.com/c/go/+/540263
Run-TryBot: David Chase <drchase@google.com>
TryBot-Result: Gopher Robot <gobot@golang.org>
Reviewed-by: Matthew Dempsky <mdempsky@google.com>

...

This commit is contained in:

David Chase 2023-11-07 17:20:35 -05:00

parent 6f5aba995f

commit b5e31780b6

10 changed files with 1522 additions and 39 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

1297

src/cmd/compile/internal/rangefunc/rangefunc_test.go Normal file

View file

File diff suppressed because it is too large Load diff