You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/06/15 00:45:00 UTC

[jira] [Commented] (GEODE-10261) VMProvider.invokeAsync does not consistently use Generic types

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

ASF subversion and git services commented on GEODE-10261:
---------------------------------------------------------

Commit c9c772ddf2618d937cf0046a74f2075ddd73e64c in geode's branch refs/heads/develop from Patrick Johnson
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=c9c772ddf2 ]

GEODE-10261: VMProvider.invokeAsync uses appropriate parameterization. (#7631)

* Cleanup use of AsyncInvocation.
* Add generic parameters to AsyncInvocation variables where they were missing.
* Cleaned up by changing single element arrays to variables.

> VMProvider.invokeAsync does not consistently use Generic types
> --------------------------------------------------------------
>
>                 Key: GEODE-10261
>                 URL: https://issues.apache.org/jira/browse/GEODE-10261
>             Project: Geode
>          Issue Type: Improvement
>          Components: tests
>    Affects Versions: 1.14.4
>            Reporter: Joris Melchior
>            Assignee: Patrick Johnsn
>            Priority: Minor
>              Labels: pull-request-available
>
> In the VMProvider class there are several invokeAsync methods with various signatures and in some cases they come with Generic type parameters and in some cases they don't.
> It's possible that some of this is influenced by the use of SerializableCallableIF vs. SerializableRunnableIF so we need to dig a little deeper to find out to what degree we need to or canĀ  make changes here.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)