Need 'this' to access 'opCall'? Was I trying to?

[Steven Schveighoffer]

On Mon, 26 Sep 2011 13:13:52 -0400, Mehrdad <wfunction at hotmail.com> wrote:

> On 9/26/2011 9:40 AM, Trass3r wrote:
>>> Well, it looks like having declared a non-static opCall makes the
>>> automatically generated constructor for the struct unusable - which  
>>> may or may not be a bug
>>
>> I do think it's a bug. Only a static opCall should interfere with the  
>> constructor.
> Yeah I agree -- should I file it as one?

Might want to add this case (as I think it is important, and doesn't yet  
seem to have an exact duplicate report) to bug 6036.  Looks like Kenji is  
on the case, and he usually comes up with a pull request :)

-Steve