lazy vals on traits cause compilation errors about scalamock HOT 7 CLOSED

Unfortunately, this turns out to be a can of worms :-( Now that you've opened my eyes to it, it turns out that there are a whole pile of issues with vals that I was previously unaware of :-(

I'm going to have to give this some thought (I'm sure that it can be solved, but I'll need to think about how best to do so). Is this causing you any immediate problems? If so, let me know and perhaps I can come up with a workaround that will get you going in the short-term until there's a long-term fix.

from scalamock.

Hi Paul,
No immediate problem, was just doing some basic familiarisation

Good luck!

Paul

From: Paul Butcher [email protected]
To: drpacman [email protected]
Sent: Wednesday, 11 January 2012, 16:37
Subject: Re: [ScalaMock] lazy vals on traits cause compilation errors (#3)

Unfortunately, this turns out to be a can of worms :-( Now that you've opened my eyes to it, it turns out that there are a whole pile of issues with vals that I was previously unaware of :-(

I'm going to have to give this some thought (I'm sure that it can be solved, but I'll need to think about how best to do so). Is this causing you any immediate problems? If so, let me know and perhaps I can come up with a workaround that will get you going in the short-term until there's a long-term fix.

Reply to this email directly or view it on GitHub:
#3 (comment)

from scalamock.

Hi Paul,
An immediate problem for us! Is there a target date to address the can of worms?
Thanks!
Jon

from scalamock.

Dang - I'm sorry about that, Jon.

The solution is, I believe, that as well as mocking the class in question, I also need to mock all of its parents. I'd love to give you a firm date, but ScalaMock is a spare time project for me.

In the interim, could you use proxy mocks for these specific cases? They shouldn't suffer from the same issue.

from scalamock.

What?! You mean to say that you are not 300% devoted to ScalaMock?? ;-)

Does ScalaMock need more contributors/committers, and should we get out there and put the word out to see if more are willing to help?

Thanks,
Jon

from scalamock.

I'd be very grateful indeed for any help - either with ScalaMock itself or with getting the word out :-)

from scalamock.

Closing this issue - ScalaMock 3 is moving to using macros instead of a compiler plugin, and I don't propose to fix outstanding issues in ScalaMock 2.x.

from scalamock.