You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@groovy.apache.org by "Eric Milles (Jira)" <ji...@apache.org> on 2021/11/17 15:36:00 UTC

[jira] [Comment Edited] (GROOVY-10374) Provide more tuple classes

    [ https://issues.apache.org/jira/browse/GROOVY-10374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17445296#comment-17445296 ] 

Eric Milles edited comment on GROOVY-10374 at 11/17/21, 3:35 PM:
-----------------------------------------------------------------

Cost vs. benefit.  Doesn't 0 through 16 offer decent enough benefit?  At what point should someone be switching to a list or stream?


was (Author: emilles):
Cost vs. benefit.  Doesn't 0 through 16 offer decent enough benefit?

> Provide more tuple classes
> --------------------------
>
>                 Key: GROOVY-10374
>                 URL: https://issues.apache.org/jira/browse/GROOVY-10374
>             Project: Groovy
>          Issue Type: Improvement
>            Reporter: Daniel Sun
>            Assignee: Daniel Sun
>            Priority: Major
>             Fix For: 4.0.0-beta-3
>
>
> As TupleN classes are widely used and current 17 tuple classes({{Tuple0}} ~ {{Tuple16}}) are not enough for some cases, we could provide more tuple classes, e.g. {{Tuple0}} ~ {{Tuple64}}.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)