Timeline for Is C# development effectively inseparable from the IDE you use?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 15, 2012 at 13:25 | comment | added | Telastyn | @Ghopper21 - The only reason to prefer explicit imports in Java (and C++ for example) is to prevent name collisions. C# made the design decision to deal with this problem via import/type aliases, since they better handle when you actually have a name collision along with the benefit of not having a bunch of boilerplate imports cluttering your source. | |
| Oct 15, 2012 at 11:36 | comment | added | Ghopper21 | That's definitely a big difference between Python and C#, but it doesn't really help me understand why there is such lack of explicitness in imports. As @pbr noted in his comment, Java (which also has the public/private distinction) is similar to Python in its cultural preference for explicit imports. | |
| Oct 15, 2012 at 11:29 | history | answered | Scott Whitlock | CC BY-SA 3.0 |