Timeline for Why are interfaces useful?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:40 | history | edited | CommunityBot | replaced http://stackoverflow.com/ with https://stackoverflow.com/ | |
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot | replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/ | |
| Sep 15, 2011 at 18:27 | comment | added | Eric Lippert | @Daniel: Yeah, I suppose it does. Its six of one and half a dozen of the other I guess! | |
| Sep 15, 2011 at 18:26 | comment | added | Daniel | @Eric: Doesn't "pattern matching" have the same problem? When I hear it I think F#/Scala/Haskell. But I guess it's a broader idea than duck-typing. | |
| Sep 15, 2011 at 17:40 | comment | added | Eric Lippert | I dislike using the term "duck typing" because it means different things to different people. We use pattern matching for the "foreach" loop because when it was designed, IEnumerable<T> was unavailable. We use pattern matching for LINQ because the C# type system is too weak to capture the "monad pattern" we need; you'd need something like the Haskell type system. | |
| Sep 15, 2011 at 16:13 | comment | added | Daniel | We're discussing this answer in chat. | |
| Sep 15, 2011 at 7:30 | history | edited | David | CC BY-SA 3.0 | added 153 characters in body |
| Sep 14, 2011 at 22:51 | history | made wiki | Post Made Community Wiki by James P. | ||
| Sep 14, 2011 at 14:25 | history | answered | David | CC BY-SA 3.0 |