Wed, 07 Sep 2016 09:22:24 -0700, Nathaniel Smith kirjoitti:
[clip]
> I wonder if there is any way we can avoid the flag, and just make this
> happen automatically when appropriate? nditer has too many "unbreak-me"
> flags already.
>
> Are there any cases where we *don't* want the copy-if-overlap b
On Mi, 2016-09-07 at 09:22 -0700, Nathaniel Smith wrote:
> On Sep 7, 2016 9:03 AM, "Sebastian Berg"
> wrote:
> >
> > Hi all,
> >
> > Pauli just opened a nice pull request [1] to add overlap detection
> to
> > the new iterator, this means adding a new iterator flag:
> >
> > `NPY_ITER_COPY_IF_OVERLA
On Sep 7, 2016 9:03 AM, "Sebastian Berg" wrote:
>
> Hi all,
>
> Pauli just opened a nice pull request [1] to add overlap detection to
> the new iterator, this means adding a new iterator flag:
>
> `NPY_ITER_COPY_IF_OVERLAP`
>
> If passed to the iterator (also exposed in python), the iterator will
Hi all,
Pauli just opened a nice pull request [1] to add overlap detection to
the new iterator, this means adding a new iterator flag:
`NPY_ITER_COPY_IF_OVERLAP`
If passed to the iterator (also exposed in python), the iterator will
copy the operands such that reading and writing should only occu
