284. Peeking Iterator

为什么80%的码农都做不了架构师？>>>   

Description

Tag： Design Difficulties： Medium

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().

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.
Follow up: How would you extend your design to be generic and work with all types, not just integer?

Solution

// Java Iterator interface reference:
// https://docs.oracle.com/javase/8/docs/api/java/util/Iterator.html
class PeekingIterator implements Iterator<Integer> {
    private Iterator<Integer> iterator;
    private Integer next;
    private boolean cache = false;
	public PeekingIterator(Iterator<Integer> iterator) {
	    // initialize any member here.
	    this.iterator = iterator;
	}

    // Returns the next element in the iteration without advancing the iterator.
	public Integer peek() {
        if (!cache && hasNext()) {
            cache = true;
            next = iterator.next();
        }
        return next;
	}

	// hasNext() and next() should behave the same as in the Iterator interface.
	// Override them if needed.
	@Override
	public Integer next() {
	    if (cache) {
            cache = false;
            return next;
        }
        return iterator.next();
	}

	@Override
	public boolean hasNext() {
	    if (cache) {
            return true;
        }
        return iterator.hasNext();
	}
}

Note: Only check next is null or not cannot determine whether there is next or not. A list can contain null integers. So it is false design.

转载于:https://my.oschina.net/liufq/blog/2250356