@Colin_Green wrote:
I see there's a way of obtaining a Vector from a Matrx row or column, and that this copies the matrix elements. I was wondering if it would be useful to have a Vector subclass that uses the matrix row or column as it's underlying storage?
Sometimes it's useful (and makes for cleaner code) to define a function as operating on Vector rather than passing in a matrix and the index of the row/column to operate on. We can use Row() and Column() today, but that introduces the overhead of copying data.
Just an idea.
Thanks.
Posts: 5
Participants: 2