Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. COBut, isn't doing it that way the same as doing the pointer arithmetic, dereferncing the result of the arithmetic, and then retrieving the this pointer of the Node? Also, I only need to do insertions to the tree all in one rush, in fact there will be about 2.557 billion insert calls with the current data set (Though due to page structure only about 255,700 buckets). Since the tree is only of order 256 there is going to be a lot of splitting in that initial rush, so, wouldn't we benefit from the increased ease of resizing the arrays?
      singulars
    2. COI'm not certain what you mean exactly -- the two code snippets I posted are functionally *identical* in every respect, and exactly the same code will be generated for them. The `&` in the 2nd snippet prevents the pointer from actually being dereferenced -- only the pointer arithmetic occurs to produce the address as a final result. (And you realise that your `**` version also does the same pointer arithmetic, right? And then does an additional pointer dereference.) Also, at no stage is any `this` pointer involved here, I'm confused about what you mean there.
      singulars
    3. COWell I misunderstood what was happening with the &(something[index]) I thought it performed the dereference then had to go back to find the pointer to the struct. What about the effect during insertions though? Not having to reallocate and copy every node in the array that needs to be resized?
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload