This project is read-only.

Feature cut: Static using statements

Topics: C# Language Design
Jun 3, 2014 at 10:43 PM
Static using statements are such a big mess! Members' name don't reflect their meaning unless contextualized with the type/typename. The presented mentioned value doesn't seem to compensate for the potential unreadability of a program, nor the possible member name collisions.
Maybe I am old school, but this feature just makes C# a little more subjective. Sometimes there is nothing wrong on typing a few more chars and make your program more readable.

A good investment on the language would be extension methods for static types and extension properties. (supported on F#, but locked for language interop...)