An unused using directive is almost certainly not “broken”, and it’s probably not misleading. It certainly is useless though. Why not produce a warning for this, so that you can remove the useless directive from your program?
Suppose we make an unused using into a warnings. Suppose you do have “warnings are errors” turned on. And suppose you create a new console project in Visual Studio. We generate you this code:
using System; class Program
static void Main(string arguments)
… which doesn’t compile. Which is better, generating code that doesn’t compile, or omitting the using directives and making you type “using System;” the first time you try to use Console.WriteLine?
Either way is a really bad user experience. So, no such feature.