News for hackers. Stuff that matters.

A comment on Implications of Rewriting a Browser Component in Rust. Parent comment

Re:Implications of Rewriting a Browser Component in Rust by pum-purum on Thursday February 28, 2019 @01:51PM (#19273954)
Compile time. For my 9k lines project it takes 20 sec to compile in debug mode and 1 minute in release. Wich is insane because I have to do a lot of runs to test things(where cargo check can't help).
[ Parent | on HN ]
Re:Implications of Rewriting a Browser Component in Rust by pum-purum on Thursday February 28, 2019 @02:03PM (#19274059)
In spite of this i'm in love with Rust
[ Parent | on HN ]
Re:Implications of Rewriting a Browser Component in Rust by herogreen on Thursday February 28, 2019 @04:43PM (#19275516)
If you modify a single line and rebuild, how much time does it takes, on average ?
[ Parent | on HN ]
Re:Implications of Rewriting a Browser Component in Rust by pum-purum on Thursday February 28, 2019 @05:37PM (#19276027)
I tried to change some constants in random places(in 1 line each time) and on average it's ~10 seconds Also compilation unit in rust is a crate. I guess if your app can be separated in different crates it can ease the pain.
[ Parent | on HN ]
Re:Implications of Rewriting a Browser Component in Rust by pum-purum on Thursday February 28, 2019 @05:37PM (#19276034)
cargo check is 3.11s
[ Parent | on HN ]