Hacker News Reader

> Just making borrow checker violations into warnings for debug builds

This is an interesting idea. I wonder what class of borrowck problems could be ignored like. Some of them can't be ignored, I think, because they would allow catastrophic things like use-after-free. But are there other violations that aren't as serious?

View on HN

If they are catastrophic, you may have to fix them to make progress. But most are not, and you can make other progress. Leaks are not. Cargo should not be dictating your work schedule.

I think this is valid reasoning. Allowing to turn errors into warnings for dev builds would probably allow for fixing issues faster. Given the UX is good.

I use todo!() a ton when building as well. Sketching out data types and signatures before diving into implementation details.

Reply on news.ycombinator.com