您的位置:首页 > 其它

284. Peeking Iterator

2016-07-19 16:30 337 查看
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.

Follow up: How would you extend your design to be generic and work with all types, not just integer?

Credits:

Special thanks to
@porker2008 for adding this problem and creating all test cases.

Subscribe to see which companies asked this question

// Below is the interface for Iterator, which is already defined for you.
// **DO NOT** modify the interface for Iterator.
class Iterator {
struct Data;
Data* data;
public:
Iterator(const vector<int>& nums);
Iterator(const Iterator& iter);
virtual ~Iterator();
// Returns the next element in the iteration.
int next();
// Returns true if the iteration has more elements.
bool hasNext() const;
};

class PeekingIterator : public Iterator {
private:
int n;
// int m;
int len;
public:
PeekingIterator(const vector<int>& nums) : Iterator(nums) {
// Initialize any member here.
// **DO NOT** save a copy of nums and manipulate it directly.
// You should only use the Iterator interface methods.
n=0;
len=nums.size();
}

// Returns the next element in the iteration without advancing the iterator.
int peek() {
return Iterator(*this).next();
}

// hasNext() and next() should behave the same as in the Iterator interface.
// Override them if needed.
int next() {
return Iterator::next();

}

bool hasNext() const {
return Iterator::hasNext();
}
};
内容来自用户分享和网络整理,不保证内容的准确性,如有侵权内容,可联系管理员处理 点击这里给我发消息
标签: