_get(Vec) and _get(Mat) should not allocate memory internally #18

Activity

1. wrtobin

   changed the title [-]_get(Vec) and _get(Mat) currently allocate the output array, but the user aware of what the array size needs to be, should change the output semantics so the memory allocation happens in user-space. Both for simplicity in terms of memory ownership and so the same array can be used to retrieve values multiple times since that is much more efficient.[/-] [+]_get(Vec) and _get(Mat) should not allocate memory internally[/+] on May 3, 2018
2. wrtobin

   self-assigned this

   on May 3, 2018
3. wrtobin

   added

   bugSomething isn't workingSomething isn't working

   enhancementNew feature or requestNew feature or request

   invalidThis doesn't seem rightThis doesn't seem right

   and removed

   bugSomething isn't workingSomething isn't working

   on May 3, 2018
4. wrtobin commented on May 3, 2018

   

   wrtobin

   on May 3, 2018

   Last edited by wrtobin

   OwnerAuthor

   More actions

   should the interface change from _get(XXX, ..... , scalar ** vals) to _get(XXX, ....., scalar * vals) since the user in now responsible for allocating the output array?

   this would reduce ambiguity