System.CommandLine is split into too many namespaces #1680
Description
I end up writing the following battery of namespaces into every project:
using System.CommandLine;
using System.CommandLine.Builder;
using System.CommandLine.Invocation;
using System.CommandLine.Parsing;
Should these namespaces be all folded into one?
This design is in conflict with .NET Framework design guidelines:
AVOID having too many namespaces.
Users of a framework should not have to import many namespaces in the most common scenarios.