[.data.table: call setalloccol for non-selfrefok tables when removing columns
#7492
+48
−34
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.

Before #7451, removing a column was always possible, because using
SETLENGTHto reduce the length of adata.tablewas mostly unchecked (and didn't cause problems in practice, modulo the allocated memory count sometimes being wrong), even if it was not created bydata.tablecode in the current R session.R_resizeVectornow requires its argument to be resizable, and freshly unserializeddata.tables don't pass the mark: ones created by older versions ofdata.tablelack the growable bit, and ones created after #7451 latest version still have a zero TRUELENGTH.Solution:
selfrefokeven if not adding new columnsjvalindicates removing a column, callsetalloccolto prevent the errorCould the test for
:=removing a column be improved? (What about list columns containingNULLs?)Fixes: #7488