Mark Harris

I would consider a pull request, definitely. But first: how would you implement the atomics on the CPU? Also, nice to hear from a Hemi user. Can you tell me...

I would like to preserve the ability to use, for example, OpenMP with Hemi. On Tue, Jun 18, 2013 at 10:37 AM, Stan Seibert [email protected]: > Since the CPU version...

I would prefer to do this in as flexible and unobtrusive way as possible. I would include it in a separate header, and just provide the sequential CPU implementation. omp...

I can't repro. I have the same GPU. Consider updating Numba, removing accelerate (outdated), and installing pyculib. Here's my packages: ~~~ [mharris@hsw213 numba_examples]$ conda list cudatoolkit # packages in environment...

Agree with @yixing-liu, we would like to be able to specify the maximum number of iterations on the command line. The reason is that we don't want to hard-code the...

Is this the right home for all of this? You already added pretty printers for thrust in thrust. Pretty printers for RMM should probably live in RMM so more of...

Selfishly, I want to be able to find RMM pretty printers in RMM so that I can use them there and in other libraries. So I guess it's OK to...

> > @harrism suggested `indexed_iterator`. This seems like the best candidate so far IMO, since the key feature of this iterator is that it provides the current index to the...

Must you force push? As you can see, doing so disassociates the comment history from the code.

Generally rebasing rather than merging is problematic with github. If you are worried about keeping the history clean, the repo should use squash merge commits when merging PRs.