aboutsummaryrefslogtreecommitdiff
path: root/api
diff options
context:
space:
mode:
authorMatthew Dempsky <mdempsky@google.com>2021-06-17 22:12:24 -0700
committerMatthew Dempsky <mdempsky@google.com>2021-06-18 22:05:09 +0000
commit9401172166ee6ac64a5a74b4a8f2aa6d3f936ea1 (patch)
treecaea706e2e06b62d9f4796f2e6228ecc3e93e7dc /api
parent57aaa19aae32a6c75a07ea8e3006fdcda7583385 (diff)
downloadgo-9401172166ee6ac64a5a74b4a8f2aa6d3f936ea1.tar.gz
go-9401172166ee6ac64a5a74b4a8f2aa6d3f936ea1.zip
runtime: clarify Frames.Next documentation
I wrote code that relied on this API, but I misunderstood the original description of the "more" result. As a consequence, my code always stopped one frame early. This CL expands the documentation to be more explicit and specifically call out my confusion (i.e., that the "more" result indicates whether the *next* Next call will return a valid Frame, and not whether this call did). Change-Id: If135f8f8c05425073d45377c4179e4f79e6bd6ca Reviewed-on: https://go-review.googlesource.com/c/go/+/329389 Run-TryBot: Matthew Dempsky <mdempsky@google.com> TryBot-Result: Go Bot <gobot@golang.org> Reviewed-by: Ian Lance Taylor <iant@golang.org> Trust: Matthew Dempsky <mdempsky@google.com>
Diffstat (limited to 'api')
0 files changed, 0 insertions, 0 deletions