Timeline for In API design, when to use/avoid ad hoc polymorphism?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 1, 2013 at 0:57 | comment | added | Erik Reppen | If hyper-explicit were easier to read/understand, how-to books would read like legalese. Also, per-type methods that all roughly do the same thing are a major DRY foul to your typical JS dev. Name for intent, not for type. What args it takes should either be obvious or very easy to look up by checking at one place in the code or in a list of accepted args at one method name in a doc. | |
| May 30, 2013 at 16:33 | history | edited | GlenPeterson | CC BY-SA 3.0 | added 15 characters in body |
| May 30, 2013 at 16:21 | comment | added | Benjamin Gruenbaum | Just letting you know that JavaScript lets you do that :) | |
| May 30, 2013 at 16:19 | history | answered | GlenPeterson | CC BY-SA 3.0 |