You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/02/09 20:13:18 UTC
[jira] [Commented] (FLINK-3382) Improve clarity of object reuse in
ReusingMutableToRegularIteratorWrapper
[ https://issues.apache.org/jira/browse/FLINK-3382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15139441#comment-15139441 ]
ASF GitHub Bot commented on FLINK-3382:
---------------------------------------
GitHub user greghogan opened a pull request:
https://github.com/apache/flink/pull/1614
[FLINK-3382] Improve clarity of object reuse in ReusingMutableToRegularIteratorWrapper
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/greghogan/flink 3382_improve_clarity_of_object_reuse_in_ReusingMutableToRegularIteratorWrapper
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/flink/pull/1614.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1614
----
----
> Improve clarity of object reuse in ReusingMutableToRegularIteratorWrapper
> -------------------------------------------------------------------------
>
> Key: FLINK-3382
> URL: https://issues.apache.org/jira/browse/FLINK-3382
> Project: Flink
> Issue Type: Improvement
> Components: Distributed Runtime
> Affects Versions: 1.0.0
> Reporter: Greg Hogan
> Assignee: Greg Hogan
> Priority: Minor
>
> Object reuse in {{ReusingMutableToRegularIteratorWrapper.hasNext()}} can be clarified by creating a single object and storing the iterator's next value into the second reference.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)