It seems it does!
Cheers,
On Thursday, 11 May 2017 00:31:48 UTC+1, Pascal Lamblin wrote:
>
> On Fri, May 05, 2017, Gilles Degottex wrote:
> > Sorry, slight confusion, by "chose the order arbitrarily" I didn't mean
> on
> > the fly. I meant be able to selection what ever order, but once for
On Fri, May 05, 2017, Gilles Degottex wrote:
> Sorry, slight confusion, by "chose the order arbitrarily" I didn't mean on
> the fly. I meant be able to selection what ever order, but once for all
> once running.
> I'm not actually changing anything once compiled.
Then it should work fine.
>
>
Sorry, slight confusion, by "chose the order arbitrarily" I didn't mean on
the fly. I meant be able to selection what ever order, but once for all
once running.
I'm not actually changing anything once compiled.
On Friday, 5 May 2017 02:56:03 UTC+1, Adam Becker wrote:
>
> I don't think this
I don't think this works. The inner function of scan will be converted to a
graph, then getting compiled inside ScanOp. If you change nonlocal variable
"order" on the fly, the change won't be reflected on the compiled function.
If the inner loop itself can be written as scan, you can just make
