Hartmut Kaiser
Hartmut Kaiser
To dynamically build this up we could do: ``` import numpy as np def _slice(x, start, size): indices = [slice(i, i+j) for i, j in zip(start, size)] return x[tuple(indices)] t...
@taless474 The problem with this code is that it passes a pure Python function to the Phylanx decorator. We will have think on how to support this kind of construct....
We have discussed this and came to the conclusion that `switch` is very similar to the already existing `where` primitive, except for the broadcasting rules to be applied to the...
I don't think that we can change the default behavior of PhySL. Even more, since Python is not very consistent about its copy semantics, some Python types are deeply copied,...
> It's not clear what you're getting at. All mutable object in Python are always references, immutable objects are always values. @parsa: integers are mutable and are not handled as...
@parsa I was able to change the value of the integer `a`, wasn't I?
@stevenrbrandt should arrays be supported by `+` ? Currently, `+` does support lists (i.e. `make_list(42) + make_list(42) == make_list(42, 42)`, is that what you need?
> @hkaiser, are changes on tests/unit/distributed/remote_add.cpp on purpose? Uhh, no. No idea how that happened - thanks for noticing.
@parsa would you mind having a look?
@ct-clmsn I think @parsa is now able to reproduce this issue. We're working on a fix as we speak...