Timeline for Repeated Instantiation of the Same Class in a Method
Current License: CC BY-SA 3.0
15 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 9, 2018 at 17:05 | vote | accept | Stevan | ||
| Apr 13, 2017 at 12:45 | history | edited | CommunityBot | replaced http://softwareengineering.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Apr 11, 2017 at 16:49 | comment | added | Frank Hileman | In C#, GeometrySplitter can be a struct, and you can have your cake and eat it too: no heap allocation, yet instantiated close to use. | |
| Apr 11, 2017 at 9:25 | comment | added | Bernhard Hiller | Strange that the answers don't focus on thread-safety (though some answers mentioned it among other things): with version B, splitter can be accessed from different threads, which might interfere with the chop method. | |
| Apr 11, 2017 at 8:11 | review | Close votes | |||
| Apr 16, 2017 at 3:06 | |||||
| Apr 10, 2017 at 19:34 | answer | added | gnasher729 | timeline score: 0 | |
| Apr 10, 2017 at 18:41 | answer | added | John Wu | timeline score: 2 | |
| Apr 10, 2017 at 11:55 | comment | added | Walfrat | To be honest I think that without a proper context I can't say A or B. If your class is only utility and there is no abstraction, you could even go for static methods : no memory, no time to allocate, one less code line. | |
| Apr 10, 2017 at 11:46 | answer | added | JacquesB | timeline score: 0 | |
| Apr 10, 2017 at 11:28 | answer | added | Pete | timeline score: 2 | |
| Apr 10, 2017 at 10:40 | answer | added | user82096 | timeline score: 10 | |
| Apr 10, 2017 at 8:12 | answer | added | civan | timeline score: -1 | |
| Apr 10, 2017 at 8:07 | answer | added | Vladimir Stokic | timeline score: 1 | |
| Apr 10, 2017 at 8:00 | review | First posts | |||
| Apr 10, 2017 at 8:27 | |||||
| Apr 10, 2017 at 7:57 | history | asked | Stevan | CC BY-SA 3.0 |