v3.0.x: datatype_optimize: keep 0-extent instances #7024
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.
Do not remove 0-extent instances while optimizing the datatype. This
is a distillation of a larger set of DDT bug fixes and optimizations
from master. George tried to cherry-pick these fixes+optimizations
back to the v3.0.x/v3.1.x branches and it resulted in a giant list of
heavily-modified cherry-picked commits (see
#6978). This did not seem like a
good idea.
George therefore distilled the critical bug fix down to this small
commit, suitable for both the v3.0.x/v3.1.x branches. See
#7019 (comment)
for details.
Signed-off-by: Jeff Squyres [email protected]
(cherry picked from commit b77ee56)
Refs #7019