Timeline for When should I use a 2-property class over a pre-built structure like a KeyValuePair?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 22, 2020 at 9:14 | comment | added | mireazma | Occam's Razor happens to be one of my primary principles. I salute mentioning it but I have to say in this particular case it dictates the opposite. I'm sorry to mention the fact that C# has multiple built-in ways to achieve the same thing with marginal benefit differences. So use basic constructs and only use "accessory" constructs only if their use is really justified. | |
| May 25, 2020 at 12:48 | comment | added | Steve | I've always considered naming things to be a "good reason" for distinguishing between what are otherwise two structurally identical classes! | |
| Jan 10, 2016 at 21:07 | comment | added | Bent | I think this is a misplaced use of Occam's razor. Secondly it is important to know what information is contained in a variable. -1. | |
| Jan 17, 2012 at 4:27 | comment | added | Evan Plaice | +1 Don't patch a whole in a boat with duct tape if it can fit a plug. | |
| Nov 29, 2011 at 13:47 | comment | added | Mal Ross |
Would you consider semantics to be "functionality that's not part of a tuple or KeyValuePair"? KeyValuePair at least has some limited form of semantics, but tuples rarely do (might be possible, depending on context) imho. Introducing a new class should give you clear semantics as a matter of course.
|
|
| Sep 13, 2011 at 17:43 | comment | added | SingleNegationElimination | "Never design what you can steal" Is about my favorite way of phrasing this. | |
| Sep 13, 2011 at 17:09 | history | edited | S.Lott | CC BY-SA 3.0 |
added 50 characters in body
|
| Sep 13, 2011 at 14:46 | history | answered | S.Lott | CC BY-SA 3.0 |