My opinion is that it is still a bug because it doesn't say clearly that float64 is not supported for this op. Also as @sbodenstein the error should happen in the bind stage. We cannot expect users to know what 1 or 0 maps to or what the error really means. The #11156 resolution is a good improvement in the error messaging. I know many ops in MXnet don't do this currently, but a better way is to check for dtypes supported for the op inputs in InferType and error accordingly even before the forward is called.
[ Full content available at: https://github.com/apache/incubator-mxnet/issues/11966 ] This message was relayed via gitbox.apache.org for [email protected]
