Jump to content

  • Log In with Google      Sign In   
  • Create Account

#ActualRavyne

Posted 03 February 2013 - 01:40 PM

You can also use a buffer of unique_ptr, but this will mean that the class is allocated seperately on the heap, instead of as a continious block in the buffer.

 

Just want to point out that, depending on what you're doing and what else is in your class, this could be perfectly fine. You'll still pay the indirection, but in terms of cache performance it might be better than if you were to have a buffer allocated as part of your class (it sounds like its heap allocated anyhow, but its not entirely clear without the source).

 

There are two downsides I can think of with this approach.

  1. The lesser issue: You can't share the data. If you needed to share it, then use shared_ptr -- you pay the cost of the reference count, but its per-shared-object, not per-sharing-object; that is, the cost is amortized across the classes sharing the object, rather than scaling up with them.
  2. The bigger issue: You essentially lose the ability to ever take any copy without destroying the original, including passing by value.

 

Enabling move semantics is also fine, this is exactly the situation it was intended for.


#1Ravyne

Posted 03 February 2013 - 01:36 PM

You can also use a buffer of unique_ptr, but this will mean that the class is allocated seperately on the heap, instead of as a continious block in the buffer.

 

Just want to point out that, depending on what you're doing and what else is in your class, this could be perfectly fine. You'll still pay the indirection, but in terms of cache performance it might be better than if you were to have a buffer allocated as part of your class (it sounds like its heap allocated anyhow, but its not entirely clear without the source).

 

The one downside I can think of with this approach is that you can't share the data. If you needed to share it, then use shared_ptr -- you pay the cost of the reference count, but its per-shared-object, not per-sharing-object; that is, the cost is amortized across the classes sharing the object, rather than scaling up with them.

 

Enabling move semantics is also fine, this is exactly the situation it was intended for.


PARTNERS