On Tue, 30 Oct 2012, Derek Gaston wrote:
On Tue, Oct 30, 2012 at 9:55 AM, Roy Stogner <royst...@ices.utexas.edu> wrote:
The only downside I can see is that "broadcast(stuff)" is more terse
than "broadcast(stuff.begin(), stuff.end())".
To me, this is a pretty big downside. I love the simplicity of
broadcast(stuff). If you want to make broadcast(stuff) turn around
and call broadcast(begin, end) that's fine with me... but I think we
should maintain the broadcast(stuff) option for the most common
cases.
Okay. "broadcast(stuff) calls broadcast(stuff.begin(), stuff.end())"
is probably what I'll do, then.
Anyone know of an existing traits class where the equivalent of
that_traits_class<T>::is_container specializes to true for container
types (i.e. any types returning iterators from begin() and end()) T?
It would be easy to create one but I'd rather not reinvent the wheel.
---
Roy
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
