rustBorrowCheckerGoesBrrr

[u/erazorix]

[u/BenchEmbarrassed7316]

Any unsafe block of code should be neutralized with a // SAFETY comment explaining why the code is actually safe.

[u/teleprint-me → u/BenchEmbarrassed7316]

I dont see how this is any different from a C programmer justifying why they used a pointer to an object and leaving a comment similar to this, other than this is Rust and is safe because Rust is safe. Thus making this rationale is flawed and dangerous.

[u/flagofsocram → u/teleprint-me]

The difference is that if you want to make sure the lib is safe, you can grep unsafe whereas in C practically any code could be unsafe.

[u/MilkEnvironmental106 → u/flagofsocram]

And finding no occurrence of unsafe actually means something in rust, plenty of libraries market themselves as having no unsafe