This problem mainly practices the implementing of the interface.
Problem:
Given an Iterator class interface with methods: next()
and hasNext()
, design and implement a PeekingIterator that support the peek()
operation -- it essentially peek() at the element that will be returned by the next call to next().
Here is an example. Assume that the iterator is initialized to the beginning of the list: [1, 2, 3]
.
Call next()
gets you 1, the first element in the list.
Now you call peek()
and it returns 2, the next element. Calling next()
after that still return 2.
You call next()
the final time and it returns 3, the last element. Calling hasNext()
after that should return false.
My solution:
// Java Iterator interface reference:
// https://docs.oracle.com/javase/8/docs/api/java/util/Iterator.html
class PeekingIterator implements Iterator<Integer> {
private Iterator it;
private Integer top;
public PeekingIterator(Iterator<Integer> iterator) {
// initialize any member here.
this.it = iterator;
top=null;
}
// Returns the next element in the iteration without advancing the iterator.
public Integer peek() {
if(top == null)
{
top = (Integer)it.next();
}
return top;
}
// hasNext() and next() should behave the same as in the Iterator interface.
// Override them if needed.
@Override
public Integer next() {
if(top == null)
return (Integer)it.next();
else
{
int val = top;
top=null;
return val;
}
}
@Override
public boolean hasNext() {
return top != null? true: it.hasNext();
}
}
Dis:
Point 1: Casting interfaces to classes. Never forget to use the cast notation to cover the type back toInteger!
2. Definition of the function peek. When using the function next(), the iterator goes to the next element, so
I should either keep the iterator not changed or note the changed iterator. I choose the later method. And
I defined the Integer top as a note!