Case Range Statement ..

[Tim Matthews]

Daniel Keep wrote:
would have written."
> 
> Can we please, please stop the useless bike-shedding on this NG?

Rather than sift through replies to a release announcement (which I have 
done since first post and still have an answer) it deserves its own 
subject. The release announcement already has:

switch case range limits
case fall through
unsigned signed conversion
build deps
bugs
others and plain old thanks for release


Sorry I must be really dumb for not understanding that subjects are a 
bad thing.

> all the alternatives proposed have SEMANTIC issues
> with them, which is much worse.


Currently we can:

import foo.bar;

or

char[] fileData = cast(char[])import("file.txt");

Whats the semantic issues with this:

case 1:
case 2:
case 3:

replaced with

case (1,3):