Online Developer Meeting (2021-07-27): Difference between revisions

Line 48: Line 48:
* jwe identified "copy expensive" inefficiency about mxArray to octave_value conversion? (some clarification needed)
* jwe identified "copy expensive" inefficiency about mxArray to octave_value conversion? (some clarification needed)
** Root of the trouble lies in historical handling of complex data?? (some clarification needed)
** Root of the trouble lies in historical handling of complex data?? (some clarification needed)
https://octave.discourse.group/t/using-std-shared-ptr-t-to-implement-copy-on-write-objects-in-octave/1436


== Previous topics ==
== Previous topics ==