Handles, new(), and Construction Patterns: Pitfalls

Pitfalls and red flags

• Treating p2 = p1 as a deep copy and corrupting expected-data queues.

• Skipping constructor defaults so objects start in partially initialized states.

• Calling methods on optional handles without null checks in shared infrastructure.

• Implementing clone() but forgetting to copy newly added fields.

• Passing the same mutable handle into parallel processes that both modify fields.

Related topics

• Back to Handles, new(), and Construction Patterns