Wait, I understand why heap_s would be allocated on the heap. But why would a tuple involving a heap_s need to be allocated on the heap assuming the heap_s already exists? The tuple should just have the NTuple and one pointer (to a heap_s) at the machine level.
This is clearly the problem, but I don't understand why this would happen (or how to work around it). Bill. On 17 August 2016 at 18:21, Kristoffer Carlsson <kcarlsso...@gmail.com> wrote: > Unless heap_s is a bitstype then the tuple will be allocated on the heap. > But you are saying it is getting allocated twice? >
