On Friday, 25 July 2014 at 09:39:23 UTC, Walter Bright wrote:
That can be special cased, too.
Seriously? Where does it end?
catch(MyTemplatedException!true) {
}
Parsing this as a proper type without a trailing identifier is a
nice feature that a lot of people use, unlike the ghastly catch
{} feature that nobody uses and should be considered harmful.
Whether we constrain the former or kill the latter, they're both
breaking changes. So why are we favouring the *bad* one?
