📎 Webclip
Object Validation: to Defer or Not?
The article separates two kinds of validation. A constructor should reject values that an object cannot represent as part of its state, such as nil or a non-String file name. Checks about whether the file exists or is actually a file belong later, when the object is used.
Reading notes#
- Constructors should stay focused on attribute initialization, but they may validate arguments that would make object state invalid.
- In the example, nil and non-String input are rejected in the constructor because the
Usersobject cannot represent those values. - Existence and file checks are done in
names, because they affect runtime behavior rather than object state. - The article describes two phases of interaction with an object: connecting and talking.
- During connecting, validation confirms that the object is suitable to work with later.
- During talking, validation may need to happen again because the situation can change over time.
- Strong typing can catch some of these errors earlier, and Kotlin null safety can remove the need for explicit nil checks.
- Ruby lacks those protections, so the checks must be done manually.
