Why doesn't dash::copy support GlobPtr as input?

[BenjaProg]

Hey, is there a reason why dash::copy doesn't accept GlobPtr as in/output?
I stumbled about this as i wanted to copy to a globmem allocated with memalloc on a remote unit.
it's just in the comments right now and I try to solve the problem another way, but I am still curious why ;-)

[fuchsto]

dash::copy is an algorithm interface, that is: it has several implementations depending on the direction (local-global, global-local, global-global) with adapter wrappers for different parameter types.
GlobPtr ranges should be supported and, at least for some variants, already are.
Apparently an adapter specialization for GlobPtr is missing for your use case. I will add it.

[fmoessbauer]

As discussed in #325 a GlobPtr does not respect the structure of values in memory. Passing a GlobPtr to dash::copy should not be allowed. Taken again the std::list example, this demonstrates why: Passing a pointer to a list element to an STL algorithm does not work because the data is not contiguous in memory. There you need full blown iterators.

Keeping that in mind, I guess we can close this issue.

[fuchsto]

@fmoessbauer That's right in principle, but std::copy accepts pointers and so should we.