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

Posted to dev@iotdb.apache.org by "Tian Jiang (JIRA)" <ji...@apache.org> on 2019/08/14 02:05:00 UTC

[jira] [Created] (IOTDB-162) Fix the semantics of hasNext() and next().

Tian Jiang created IOTDB-162:
--------------------------------

             Summary: Fix the semantics of hasNext() and next().
                 Key: IOTDB-162
                 URL: https://issues.apache.org/jira/browse/IOTDB-162
             Project: Apache IoTDB
          Issue Type: Improvement
            Reporter: Tian Jiang
         Attachments: image-2019-08-14-09-50-05-929.png

Some definitions of hasNext() and next() are misleading, for example, the following actually means hasCurrent rather than hasNext, say, when curIdx = timeLength - 1, it will true while actually there is not the next value.

Such definitions conflict the hasNext() and next() defined and widely used in Java Iterator, and cause confusion to those who are not so familiar with the code.

!image-2019-08-14-09-50-05-929.png!



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)