Dive into the bold design choices of Rust! In this video, we explore how Rust sets itself apart from traditional object-oriented languages like C++, Java, and C# by eliminating conventional constructors. Discover how this unique approach impacts object initialization, encapsulation, and inheritance. Whether you’re a seasoned developer or new to Rust, you’ll gain valuable insights into its innovative architecture. 

Free Rust training: https://letsgetrusty.com/bootcamp

Chapter:
0:00 Intro
0:25 C++ constructors
2:34 Rust's Approach

Let's Get Rusty

Rust has made bold design choices by eliminating traditional constructors used in languages like C++ and Java. Instead, it prioritizes explicit initialization, simplicity, and composition over inheritance. This design minimizes common pitfalls associated with object creation and error handling in traditional OOP languages. Rust's strict requirement for explicit field initialization enhances safety and prevents undefined behavior. Additionally, Rust supports creating objects with default values through its default trait. These features make Rust a compelling choice for developers from higher-level languages.

The genius of Rust constructors

Build state in types is what blows my mind in Rust. I mimicked it in Go to the extend that was possible, but it is all done pretty much at runtime, where as Rust can enforce correctness at compile time.

Mix feelings about this. Object initialisation requires design in any language, that usually depends on the object’s lifecycle and allowed operations in different scopes the object is manipulated. That’s why builders and factories exist. Rust forcing to initialize object’s member attributes feels less flexible for object initialisation design, but ends up being less error-prone for cases where object design is overlooked (for any reason). I tend to take with a pinch of salt comments like “we could forget to do X” or “if you don’t fully know how the language Y works, you’ll have a bug”.
Is there really out there a language that you can just code carelessly and be productive ready, because the language protected itself from inexperienced developers?