Re: [Libmesh-devel] Exposing _boundary_side_id / Optimizing boundary_ids()

[Roy S. <roy...@ic...>]

On Wed, 20 Jun 2018, Derek Gaston wrote:

> On Wed, Jun 20, 2018 at 1:56 PM Roy Stogner <roy...@ic...> wrote:
>       Hmm... would it be sane to write a shim iterator class, just something
>       to prevent conversion to std::data_type_now_locked_in_stone::iterator,
>       and then return a pair of those?
> 
> Can we just assume that everyone will capture the return value using
> "auto" so it's not a problem?  :-)

Well, we definitely *can*, and I'm lazy enough that I'm tempted...

> From some snooping around it looks like MultiMap returns
> BidirectionalIterators... could we just make a std::pair of those
> and return them?

I wish.  Those aren't a real type, though, they're what the C++
standards people call "concepts" or "named requirements".  But
language support for concepts has been getting deferred for years, and
there's no underlying class you can attach them to.
---
Roy