The reason why Cumo returns 0-dimensional array instead of Ruby numeric object is, to avoid cudaMemcpy from GPU to CPU for performance.
For compatibility between Numo and Cumo, I propose to change behavior of Numo to return 0-dimensional NArray directly without converting it into Ruby numeric object.
This is a feedback from Cumo implementation. https://speakerdeck.com/sonots/fast-numerical-computing-and-deep-learning-in-ruby-with-cumo?slide=42
Numo:
Cumo:
The reason why Cumo returns 0-dimensional array instead of Ruby numeric object is, to avoid cudaMemcpy from GPU to CPU for performance.
For compatibility between Numo and Cumo, I propose to change behavior of Numo to return 0-dimensional NArray directly without converting it into Ruby numeric object.