On Tue, May 24, 2016 at 1:31 PM, Alan Isaac <alan.is...@gmail.com> wrote: > On 5/24/2016 1:19 PM, Stephan Hoyer wrote: >> >> the int ** 2 example feels quite compelling to me > > > > Yes, but that one case is trivial: a*a
Right, but you'd have to know to change your code when numpy makes this change. Your code will suddenly have a new datatype, that you may be passing into other code, which may generate different results, that will be hard to track down. > And at least as compelling is not have a**-2 fail I imagine that's about an order of magnitude less common in real code, but an error seems an acceptable result to me, so I know I have to do a ** -2.0 > and not being tricked by say np.arange(10)**10. > The latter is a promise of hidden errors. It's a well-understood promise though - you always have to be careful of integer overflow. Best, Matthew _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@scipy.org https://mail.scipy.org/mailman/listinfo/numpy-discussion
