Rad, thanks for the input everyone! I'm anticipating some friction with using FFI with the C API since it's considered unsafe in Rust; difficulty of integrating will depend on the nuances of the C API as HY mentioned...
Going to go ahead and dive in. Will be back eventually for feedback / input! Zach Boldyga Scalabull | Founder 1 (866) 846-8771 x 101 On Wed, Jan 30, 2019 at 12:02 AM HY Chen <[email protected]> wrote: > I have tried to create a a module via existing rust FFI generators but > failed. It seems like you have to think a lot more than just translate the > C api to make it work. It's better understand the C API first and make sure > it won't introduce new problems in rust. > > HY > > Pedro Larroy <[email protected]> 于2019年1月30日周三 上午4:35写道： > > > I have been thinking about this and I find really exciting to have > > Rust bindings and bring a powerful framework like MXNet to the Rust > > community and to native applications in a convenient Rust crate. I > > would love to see this happen. I think basically MXNet needs to be > > wrapped in a Rust crate via FFI / C Bindings. > > > > Pedro. > > > > On Tue, Jan 29, 2019 at 11:05 AM Zach Boldyga <[email protected]> > wrote: > > > > > > Hey y'all! > > > > > > I'm thinking about spending this week working on a rust client lib for > > > MXNet. saw a little bit of chatter about this in the github issues and > no > > > strong existing crates at the moment. Any pointers on approaching this > > in a > > > way that will lead to it being adopted as an officially supported > client > > > library? And overall yay/nay on whether adding a Rust lib makes sense & > > why > > > / why not? > > > > > > Zach Boldyga > > > Scalabull | Founder > > > 1 (866) 846-8771 x 101 > > >
