Proper way to fix ice-on-valid-code?

[Jason House]

I'm a bit annoyed that issue 1719 [1] got closed with a claim that d 1.026
and d 2.010 fixed the problem.  

There was discussion of this around the time of the release.  Rather than
making valid code work as expected, Walter made the compiler issue an error
(and avoid a compiler crash).  I was ok with this as a temporary fix, and
was patiently awaiting a proper fix.  I now the hack breaks code inside
Tango.

Walter did post a workaround that basically avoided using an interface with
scope:
  scope X x = new X(); // requires using exact type
  I i = x;

Of course, this does not work with object factories.

I guess I'm just really disapointed to see this...  Maybe a more proper
thing is for me to reopen 1719, but I don't want to battle Walter with back
and forth opening and closing of bugs.  Should I instead post a new
bug/feature request?

[1] http://d.puremagic.com/issues/show_bug.cgi?id=1719