Timeline for Modularity vs pure functions
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 23, 2022 at 5:39 | comment | added | S.D. | doThisAndDoThat function names are generally a sign of tight coupling. | |
| Sep 20, 2022 at 15:15 | vote | accept | deSKase | ||
| Sep 20, 2022 at 9:04 | history | edited | deSKase | CC BY-SA 4.0 | pseudocode improved |
| Sep 19, 2022 at 19:15 | answer | added | Christophe | timeline score: 1 | |
| Sep 19, 2022 at 15:42 | answer | added | amon | timeline score: 2 | |
| Sep 19, 2022 at 13:00 | comment | added | Philip Kendall | Your add_<foo>_to_t functions don't look pure to me. Something that doesn't return a value is neither a no-op or impure, because the other thing it can do is to have a side effect. | |
| S Sep 19, 2022 at 12:16 | review | First questions | |||
| Sep 19, 2022 at 19:17 | |||||
| S Sep 19, 2022 at 12:16 | history | asked | deSKase | CC BY-SA 4.0 |