c# - What's the value in removing and/or sorting Usings? -
i've run remove , sort usings matter of course, because seems right thing do. got wondering: why this?
certainly, there's benefit clean & compact code. , there must benefit if ms took time have menu item in vs.
can answer: why this? compile-time or run-time (or other) benefits removing and/or sorting usings?
as @craig-w mentions, there's small compile time performance improvement.
the way compiler works, when encounters type, looks in current namespace, , starts searching each namespace using directive in order presented until finds type it's looking for.
there's excellent writeup on in book clr via c# jeffrey richter (http://www.amazon.com/clr-via-4th-developer-reference/dp/0735667454/ref=sr_1_1?ie=utf8&qid=1417806042&sr=8-1&keywords=clr+via+c%23)
as why ms provided menu option, imagine enough internal developers asking for same reasons mention: cleaner, more concise code.
Comments
Post a Comment