You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@mxnet.apache.org by GitBox <gi...@apache.org> on 2019/02/27 08:38:52 UTC

[GitHub] wkcn commented on issue #14253: [RFC] Introducing NumPy-compatible coding experience into MXNet

wkcn commented on issue #14253: [RFC] Introducing NumPy-compatible coding experience into MXNet
URL: https://github.com/apache/incubator-mxnet/issues/14253#issuecomment-467772882
 
 
   +1 for this RFC.
   
   It will be more flexible to use MXNet, especially in slicing, and I hope mx.numpy could eliminate the divergence between mx.nd and mx.sym.  : )
   
   I wonder how to implement mx.numpy: using Python ast  module to extract the abstract syntax tree then run them on JIT, or implement it on Python entirely? We should also focus on the deployment of mx.numpy.
   
   I do not think F.numpy.dot is a good idea, since it is confusing that mx.numpy, mx.nd.numpy and mx.sym.numpy all exist. We only need mx.numpy to support mx.numpy.dot(a_nd, b_nd) and mx.numpy.dot(a_sym, b_sym).

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services