News for hackers. Stuff that matters.
Re:How to not rewrite it in Rust by Skunkleton on Wednesday October 23, 2019 @02:33PM (#21337433)
(4) You want to develop new components in rust, but it has to integrate with your existing components somehow.
Re:How to not rewrite it in Rust by pyython on Wednesday October 23, 2019 @03:54PM (#21338243)
How about (5) you're trying to learn Rust and you need a project to work on? Irresponsible for production code, but perfectly valid for a weekend project. And in my experience can be a great way to learn the quirks of a particular language!
Re:How to not rewrite it in Rust by zbentley on Wednesday October 23, 2019 @03:01PM (#21337714)
Why not use ffi for this case? Many languages have robust support for linking to Rust code.
Re:How to not rewrite it in Rust by gameswithgo on Wednesday October 23, 2019 @03:38PM (#21338095)
yeah sometimes that makes sense. if the lib in question in small enough it might be more valuable to port, so avoid having a multi language project, and avoid the effort of the ffi.

at least Rust -> C ffi is zero cost (usually)

Re:How to not rewrite it in Rust by viraptor on Wednesday October 23, 2019 @08:41PM (#21340571)
Having everything available in Rust code also means you don't have to do lots of extra work for cross-compilation.
Re:How to not rewrite it in Rust by saagarjha on Wednesday October 23, 2019 @11:45PM (#21341486)
How does Rust help you if you have to cross-compile?
Re:How to not rewrite it in Rust by viraptor on Thursday October 24, 2019 @06:23AM (#21343156)
You can compile rust in one go. If you rely on native libraries, you need to be able to link them during cargo build and that's painful to set up. Not impossible... just really annoying to manage.
Re:How to not rewrite it in Rust by saghm on Thursday October 24, 2019 @12:07AM (#21341559)
I'm not positive, but I think GP intended to refer to idea that you would need to multiple compilers to compile the project rather than cross-compiling to another platform.