Timeline for How to design extensible data aggregation code to avoid manual updates in multiple places?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7 at 11:10 | answer | added | Filip Milovanović | timeline score: 0 | |
| Oct 1 at 14:46 | history | became hot network question | |||
| Oct 1 at 8:18 | answer | added | Arseni Mourzenko | timeline score: 5 | |
| Oct 1 at 7:28 | comment | added | freakish | Some languages and/or tools will warn you if you have an unused variable/field, or that you only write to it, not read and vice versa (e.g. Rust does this). But there's absolutely no way for a compiler to warn you that it needs to be used in two places. So either you just discipline yourself or add an intermediate data structure between the steps. Which increases code bloat (and potentially degrades performance) but might be worth it. | |
| S Oct 1 at 6:39 | review | First questions | |||
| Oct 1 at 11:47 | |||||
| S Oct 1 at 6:39 | history | asked | Tank | CC BY-SA 4.0 |