|
|
Log in / Subscribe / Register

Non-technical advantages of rustc

Non-technical advantages of rustc

Posted Nov 15, 2025 10:37 UTC (Sat) by farnz (subscriber, #17727)
In reply to: Code Review by tialaramex
Parent article: Rust in Android: move fast and fix things (Google Security Blog)

Your comment about improving a diagnostic brings up one thing that the rustc project gets right, and that helps Rust's adoption; diagnostics (both lints and failures) are continuously being improved, and the people behind the compiler are supportive of efforts to make the diagnostics better.

This sort of work isn't always seen as valuable - after all, an error like "problem in type unification: cannot meet constraints for arg, arg is parameterized type T, T is required to implement Debug + Send + Sync, but supplied value param has type MyParamType, which implements Display + Send + Sync + Unpin + RefUnwindSafe + UnwindSafe" contains all the information you could possibly need to diagnose the bug, but "param is of type MyParamType, which does not implement Debug, which is required in funct(param) by fn funct<T: Debug>(arg: T)" is so much more helpful to the user, even though it has strictly less information than the first form.


to post comments

Non-technical advantages of rustc

Posted Nov 16, 2025 2:37 UTC (Sun) by tialaramex (subscriber, #21167) [Link]

AIUI One of the things which consciously drove that, and which is as often a source of conflict on LWN as the claims of improved correctness, is Rust's tag line: "A language empowering everyone to build reliable and efficient software"

Because we're not "empowering everyone" if we've made it easy for you to attend our conference but practically impossible to understand our compiler warnings.

Seeing this tag line from other angles also encourages other technical changes, for example Rust often goes out of its way to have the obvious thing you'd write be efficient rather than try to teach Rust programmers to write something else that is already efficient - for beginners this means it's more likely that the Rust program you wrote, though perhaps not very sophisticated, has excellent performance anyway, but even for experienced Rust programmers it means often you don't need to figure out a clever way to write what you meant efficiently, the obvious way to write it is optimised anyway.


Copyright © 2026, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds