geode-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alyssa Kim (JIRA)" <j...@apache.org>
Subject [jira] [Assigned] (GEODE-1577) Unhelpful generic types on Execution.execute
Date Sun, 26 Mar 2017 04:45:41 GMT

     [ https://issues.apache.org/jira/browse/GEODE-1577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alyssa Kim reassigned GEODE-1577:
---------------------------------

    Assignee: Alyssa Kim  (was: Dan Smith)

> Unhelpful generic types on Execution.execute
> --------------------------------------------
>
>                 Key: GEODE-1577
>                 URL: https://issues.apache.org/jira/browse/GEODE-1577
>             Project: Geode
>          Issue Type: Bug
>          Components: functions
>            Reporter: Dan Smith
>            Assignee: Alyssa Kim
>
> The execute methods of the function service Execution class returns a ResultCollector
with wildcards for the type.
> {code}  
> public ResultCollector<?, ?> execute(
>       Function function) throws FunctionException;
> {code}
> Wildcards are supposed to be used in APIs where the type doesn't matter, for example
counting the elements in a list. By returning a ResultCollector with wildcards, we're essentially
forcing the user to cast the result collector.
> At a minimum they should be able to pick the type of result collector
> {code}
>   public <T,S> ResultCollector<T, S> execute(
>       Function function) throws FunctionException;
> {code}
> But maybe it would make more sense to parameterize Execution itself. Then the compiler
could ensure that the types used by withCollector and the types used by execute match.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message