[
https://issues.apache.org/jira/browse/TINKERPOP-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18077819#comment-18077819
]
ASF GitHub Bot commented on TINKERPOP-3244:
-------------------------------------------
L0Lmaker commented on PR #3416:
URL: https://github.com/apache/tinkerpop/pull/3416#issuecomment-4364192888
Thanks @spmallette! Updated the commit message — the trailer now reads
`Assisted-by: Claude Code:claude-opus-4-7`. Branch force-pushed at `d396815e4c`.
For future reference (and anyone else interpreting the AGENTS.md template),
I read `AGENT_NAME:MODEL_VERSION [TOOL]` literally and matched the existing
precedent in `0531cbb7d0` (`Assisted-by: Kiro:claude-opus-4.6 [kiro-cli]`),
which appears to have hit the same ambiguity. Happy to look at AGENTS.md
wording in a separate PR if helpful.
> Add next(n) batch iteration to gremlin-go for GLV parity
> --------------------------------------------------------
>
> Key: TINKERPOP-3244
> URL: https://issues.apache.org/jira/browse/TINKERPOP-3244
> Project: TinkerPop
> Issue Type: Improvement
> Components: driver
> Affects Versions: 3.7.5, 3.8.1
> Reporter: Taylor Riggan
> Priority: Minor
>
> The Java, Python, and .NET GLVs all support `next\(n\)` on Traversal to
> retrieve multiple results at once, but gremlin-go only supports single-item
> `Next()` returning `(*Result, error)`. This creates an API inconsistency
> across GLVs that makes it harder to write portable examples and documentation.
> Currently, users must manually collect results from `GetResultSet()` +
> `One()` in a loop to achieve the same behavior. A `Next(n int) ([]*Result,
> error)` method on `Traversal` would bring gremlin-go in line with the other
> GLVs.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
