On Tue, Jul 3, 2018 at 12:11 PM, Stephan Hoyer <sho...@gmail.com> wrote:
> On Tue, Jul 3, 2018 at 7:13 AM Marten van Kerkwijk < > m.h.vankerkw...@gmail.com> wrote: > >> Overall, would one way to move forward be to merge the first PR (flexible >> and frozen) and defer the broadcastable dimensions? >> > > This would have my support. > > I have similar misgivings about broadcastable dimensions to those raised > by Nathaniel. > > In particular, I wonder if there is some way to make use of this > functionality internally in NumPy for functions like all_equal() without > exposing it as part of the external gufunc API. > > OK, so let me explicitly ask whether there are any objections to going forward with flexible and frozen dimensions, but deferring on broadcastable ones until more compelling use cases have been identified? Thanks, Marten p.s. I adjusted the "acceptance PR" to reflect this: https://github.com/numpy/numpy/pull/11429
_______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion
