Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

There is things you really can't do by yourself. I've been working on porting some large codebases to Rust lately to experiment with fixing memory safety bugs. There is just no way you can write 100k LOC in a week of production code with tons of tests etc. Even "10X" engineers just can't type that fast.


How would one even know if the port of 100k LOC was successful? Are there language-agnostic tests (CLI STDIN/STDOUT) or similar involved?


I was using large official test suites + lots of tests I generated that test input/ output is byte identical over thousands of commands.

You wouldn’t want to ship it straight to prod but it’s a start.


Vibes, man!


even if that were true its the exact opposite point the article is trying to make


What language you are trying to port from?


C to Rust. c2rust exists but isn’t particularly helpful if you want it to be safe/ performant code anyway.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: