I would also prefer separate functions. These are much easier to understand that custom operator overloads.
Side note: implementing this class with __array_ufunc__ for ndarray @ cvec actually isn't possible to do currently, until we fix this bug: https://github.com/numpy/numpy/issues/9028 On Sat, Jul 1, 2017 at 5:31 PM, Juan Nunez-Iglesias <jni.s...@gmail.com> wrote: > I’m with Nathaniel on this one. Subclasses make code harder to read and > reason about because you now have to be sure of the exact type of things > that users are passing you — which are array-like but subtly different. > > On 2 Jul 2017, 9:46 AM +1000, Marten van Kerkwijk < > m.h.vankerkw...@gmail.com>, wrote: > > I'm not sure there is *that* much against a class that basically just > passes through views of itself inside `__matmul__` and `__rmatmul__` > or calls new gufuncs, but I think the lower hurdle is to first get > those gufuncs implemented. > -- Marten > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > > > _______________________________________________ > NumPy-Discussion mailing list > NumPy-Discussion@python.org > https://mail.python.org/mailman/listinfo/numpy-discussion > >
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
