Avoid usedElements around code that modifys that value (#3488)

Followup to #3486, I wonder if it isn't a little more clear this way,
which avoids the confusion of usedElements being changed
while we are using it.

In general I think it's best to only use usedElements in the most
internal methods, and to call size() otherwise.

1 files changed, 6 insertions, 6 deletions

diff --git a/src/mixed_arena.h b/src/mixed_arena.h
index b4822680b..4d2e24542 100644
--- a/src/mixed_arena.h
+++ b/src/mixed_arena.h
@@ -368,21 +368,21 @@ public:
   // C-API
 
   void insertAt(size_t index, T item) {
-    assert(index <= usedElements); // appending is ok
-    resize(usedElements + 1);
-    for (auto i = usedElements - 1; i > index; --i) {
+    assert(index <= size()); // appending is ok
+    resize(size() + 1);
+    for (auto i = size() - 1; i > index; --i) {
       data[i] = data[i - 1];
     }
     data[index] = item;
   }
 
   T removeAt(size_t index) {
-    assert(index < usedElements);
+    assert(index < size());
     auto item = data[index];
-    for (auto i = index; i < usedElements - 1; ++i) {
+    for (auto i = index; i < size() - 1; ++i) {
       data[i] = data[i + 1];
     }
-    resize(usedElements - 1);
+    resize(size() - 1);
     return item;
   }
 };