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

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

On Wed, 20 Jun 2018, Derek Gaston wrote:

> It turns out that I wasn't reusing the vector as well as I thought -
> which was causing some of the re-allocation.  That is solved now so
> the re-allocation is at a minimal level.  I'm doing a reserve()
> myself to put plenty of space in that vector to keep down
> re-allocation.

Good to hear!

> That said: I would still like to think about an interface that
> doesn't involve any allocation.  Even just one that returns the
> results of the equal_range() would be nice.

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?
---
Roy