Timeline for Using output arguments in C++ to avoid dynamic allocations
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 18, 2020 at 13:13 | vote | accept | cube | ||
| Nov 18, 2020 at 13:13 | vote | accept | cube | ||
| Nov 18, 2020 at 13:13 | |||||
| Nov 18, 2020 at 12:50 | vote | accept | cube | ||
| Nov 18, 2020 at 13:12 | |||||
| Nov 4, 2020 at 9:05 | history | edited | JayZ | CC BY-SA 4.0 | edited body; added 69 characters in body |
| Nov 3, 2020 at 19:49 | comment | added | Deduplicator | One should not needlessly write inefficient code. Clarity is generally sufficient to trump small efficiencies, but those should only be tolerated where doing so actually saves effort. One should care whether the current code is liable to be a bottleneck. If that is sufficiently likely, one has to measure and potentially tinker. If that is sufficiently unlikely, one gets to expend the saved effort where it matters. Be that finding and fixing a bottleneck, adding a feature, the next great thing, or the big party. | |
| Nov 3, 2020 at 14:01 | history | answered | JayZ | CC BY-SA 4.0 |