The comma separated namespace list in a uses
statement feels somewhat out of date these days. It could be a simple enhancement to allow multiple, consecutive uses
statements. Each statement would optionally support a comma separate list of namespaces as currently, or could identify a single namespace.
If used, multiple uses
clauses must be contiguous. That is you could not have a uses
statement followed by a type
declaration followed by a further uses
statement.
Contiguous uses
statements would have the same effect as if they were one single statement with all namespaces listed in the order in which they occur in the separate statements.
That is:
uses A;
uses B;
uses C;
Would be equivalent to:
uses A, B;
uses C;
Which would be equivalent to:
uses A, B, C;
This would then provide flexibility in organising uses clauses which could be grouped by root namespace (for example):
uses
System,
System.Net;
uses
Microsoft.AspNetCore.Mvc,
Microsoft.Extensions.Logging;
uses
MyApp.MyNamespace;
Or, more practically, to list namespaces as discrete references that can be more easily modified without breaking valid termination of the statements (since each is individually moveable/removable, irrespective of current/starting position in the list).
uses A;
uses B;
uses C;
A small change (?) and granted not exactly a massive leap forward in terms of language technology, but might be worth considering ?