Timeline for What are the approaches of protecting against partially initialized objects?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14 at 15:49 | comment | added | Sophie Swett |
"But in multi-threaded C/C++/Java this also means […]" – Even in Java? I find that incredibly surprising! My understanding of that statement would have been that the expression new Singleton() doesn't finish evaluating until the constructor has finished running, and the assignment doesn't occur until its right-hand side has finished evaluating. Which of these is not true for Java?
|
|
| Jun 13 at 14:33 | history | edited | André L F S Bacci | CC BY-SA 4.0 |
added 866 characters in body
|
| Jun 12 at 21:06 | history | edited | André L F S Bacci | CC BY-SA 4.0 |
added 1762 characters in body
|
| Jun 12 at 16:36 | comment | added | Bbrk24 |
Swift and Objective-C have something similar to the last one; In Swift it's spelled init?(...), and in Objective-C it's done by marking the return type as instancetype _Nullable or instancetype __nullable rather than just instancetype.
|
|
| Jun 12 at 16:15 | history | answered | André L F S Bacci | CC BY-SA 4.0 |