X10

exception is thrown when calling next() on a PolyRegion iterator without calling hasNext first

Details

  • Number of attachments :
    0

Description

RTC-864

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Mikio Takeuchi added a comment -

This is a native x10 issue

Show
Mikio Takeuchi added a comment - This is a native x10 issue
Hide
Permalink
David Grove added a comment -

defer all non-critical 2.1.2 issues to 2.2.

Show
David Grove added a comment - defer all non-critical 2.1.2 issues to 2.2.
Hide
Permalink
David Grove added a comment -

Problem is in iterator of the BandedRegion. Since that's a PolyRegion, it probably means that some part of PolyRegion isn't working correctly. Problem is in class library (shows up in either backend).

Show
David Grove added a comment - Problem is in iterator of the BandedRegion. Since that's a PolyRegion, it probably means that some part of PolyRegion isn't working correctly. Problem is in class library (shows up in either backend).
Hide
Permalink
David Grove added a comment -

bug is that Iterator on PolyScanner was relying on hasNext() and next() being called in lockstep because hasNext actually modified the iterator's state to prepare for the next call to next().

Show
David Grove added a comment - bug is that Iterator on PolyScanner was relying on hasNext() and next() being called in lockstep because hasNext actually modified the iterator's state to prepare for the next call to next().
Hide
Permalink
David Grove added a comment -

fixed in 21273.

Show
David Grove added a comment - fixed in 21273.
Hide
Permalink
David Grove added a comment -

bulk close of all 2.2.0 resolved issues.

Show
David Grove added a comment - bulk close of all 2.2.0 resolved issues.

People

  • Assignee:
    David Grove
    Reporter:
    X10TEST
Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved: