[SciPy-User] Q: Provide .H for numpy arrays?
Thu Oct 14 13:51:28 CDT 2010
On Thu, Oct 14, 2010 at 10:05 AM, Dag Sverre Seljebotn
> Of course, it is likely a lot of work. But the existance of the
> possibility of this path in the long run makes me negative towards the
> proposal of just implementing "arr.H" the easy way (making a copy) in
> the short run because it would make it impossible to introduce something
> much more useful later on. A naive implementation of "arr.H" would not
> work well with gigabyte-sized arrays on most computers, and is always
> available as "arr.T.conjugate()" anyway, which is more explicit about
> making a copy.
+1 to your view: anything making an explicit copy of something
potentially large better have a very visible '()' in there.
More information about the SciPy-User