Timeline for Simple builder pattern implementation for building immutable objects
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 23, 2017 at 11:25 | answer | added | Jilles van Gurp | timeline score: 3 | |
| Feb 23, 2017 at 9:34 | answer | added | Roel Spilker | timeline score: 4 | |
| May 5, 2016 at 1:13 | history | edited | Jamal | CC BY-SA 3.0 |
added 37 characters in body; edited title
|
| May 4, 2016 at 21:05 | vote | accept | Levent Divilioglu | ||
| May 4, 2016 at 17:53 | answer | added | Thijs Riezebeek | timeline score: 12 | |
| May 4, 2016 at 7:25 | history | tweeted | twitter.com/StackCodeReview/status/727761034208022528 | ||
| May 4, 2016 at 6:17 | history | edited | Levent Divilioglu |
Why someone tag this with factory pattern ? This is a builder pattern, removed the tag.
|
|
| May 3, 2016 at 16:26 | history | edited | 200_success |
edited tags
|
|
| May 3, 2016 at 15:59 | answer | added | coderodde | timeline score: 4 | |
| May 3, 2016 at 15:50 | comment | added | Levent Divilioglu | It is a builder pattern structure to use flexible dot notation however each instance of Person will be unique, thus immutable. If build() called several times inside a Person constructor, each Person object will be immutable and unique, that was my intention. And the Person objects thread-safe as all member variables are final, are settable only for once. | |
| May 3, 2016 at 15:24 | comment | added | coderodde |
The builder object maintains a state. If you call build() several times in a row, you will create as much identical persons. Is that your intention?
|
|
| May 3, 2016 at 15:11 | history | asked | Levent Divilioglu | CC BY-SA 3.0 |