More tk

discuss as desired.
Sure. I think everything I suggested is API extensions anyway. Just thought
I'd throw the idea out.

On Thu, Oct 30, 2014 at 11:49 AM, Robert Carlsen <notifications@github.com>
wrote:

> In src/toolkit/resource_buff.h:
>
> > @@ -101,6 +101,16 @@ class ResourceBuff {
> >    /// store's current inventoryNum or the specified number is negative.
> >    Manifest PopN(int num);
> >
> > +  /// Peek returns the next resource that will be popped from the buffer
> > +  /// without actually removing it from the buffer.
> > +  template <class T>
> > +  typename T::Ptr Peek() {
>
> I thought about it, but for now at least, I decided that most of the other
> extensions I could think of were served reasonably well by pop and pushing.
> This single function in particular will solve multiple uses in the cycamore
> and other archetypes I've made/seen. I'm not so sure about multi and range
> peeks (yet).
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/cyclus/cyclus/pull/1037/files#r19618092>.
>



-- 
Matthew Gidden
Ph.D. Candidate, Nuclear Engineering
The University of Wisconsin -- Madison
Ph. 225.892.3192