I think there’s a broad issue that need resolution: how do you know when a function’s output takes control of the memory used by its arguments?
— John On Aug 31, 2014, at 11:45 AM, Ethan Anderes <[email protected]> wrote: > Yeah, I can see your point John. It's probably not reasonable to make a new > AliasedArray type. > > For me I think the education would address the difference between vec, for > example, when used inside another function, eg x = sin(vec(a)), or the memory > overlap case, eg x = vec(a). This stung me at one point. When ArrayViews > lands as slicing in Base I should take a shot at a PR for the docs. > > Cheers
