I noticed the managed ArrayList was depricated. We now have to pass the allocator in to all functions that might allocate memory. There is a footgun here in that if you pass in a different allocator to, say, ensureTotalCapacityPrecise than was originally used, that function might try to free memory with a different allocator than it was allocated with. This seems like it could be a Bad Thing™. Since we must pass the same allocator each time, what is the logic behind ArrayIssue not remembering it for us?
#ArrayList Issue
1 messages · Page 1 of 1 (latest)