i want to second this feature request! although some rather outdated and unmaintained rust-bindings for mxnet already exist ([mxnet-rs](https://github.com/jakelee8/mxnet-rs)) and the utilization of mxnets c-bindings looks more ore less trival given rusts ffi capabilities (see: [rust-bindgen](https://github.com/rust-lang-nursery/rust-bindgen)), i would really like to see rust-bindings officially supported, reliable maintained and a little bit better documented.
beside the fact, that rust is becoming more and more popular as very fast and secure general purpose programming language, it's an exceptional efficient solution to generate webassambly components (see: https://github.com/rustwasm). that's a field of applications, where python based development approaches usually fail. but because of mxnets excellent low level binding capabilities resp. hybrid nature, DNN creation utilizing python based gluon and final deployment via rust resp. wasm, looks like a very attractive and promising combination to overcome this shortcomings. we recently saw a lot of interest and more advanced efforts to solve this issue in the TVM project ([tvm-rust](https://github.com/ehsanmok/tvm-rust), [tvm.rs](https://github.com/nhynes/tvm-rs)), which could be seen as another workaround to archive this goal, nevertheless i would see some kind of official rust support within the mxnet project as a very useful improvement. [ Full content available at: https://github.com/apache/incubator-mxnet/issues/10698 ] This message was relayed via gitbox.apache.org for [email protected]
