Clarify ownership model of CiffComponent::pData_ #1930
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a stepping stone to some other changes that I would like to make to
DataBuf
. In particular, I would like to get rid of therelease
method and instead usestd::move
for ownership transfers ofDataBuf
.This changes simplifies the ownership model of
CiffComponent::pData_
. It is usually a pointer into read-only memory owned by somebody else, but whenisAllocated_ == true
, it owns the memory. This, combined with the fact that we sometimes do arithmetic on the pointer, makes me nervous. I have changed it so thatpData_
always points to data owned by somebody else. I added a field namedstorage_
for whenCiffComponent
needs to own the data itself.