I have almost finished the implementation, save some polishing and testing. The current solution is not in the backend, but alongside `Block`. To allow one piece of code to support both `ndarray` and `symbol` at the same time, it uses the same idea as `HybridBlock`. The difference is that for `HybridBlock` there might be parameters inside and it is necessary to instantiate and possibly hybridize it before use, whereas an operator has its interfaces exposed in `mxnet.ndarray` and `mxnet.symbol`, and should look the same as other operators 'imported' from the backend.
I think this is probably a decision on the design, as it means a new interface for developing new operators. [ Full content available at: https://github.com/apache/incubator-mxnet/issues/10840 ] This message was relayed via gitbox.apache.org for [email protected]
