Re: Fwd: [Lift] Cleaning up warnings

2009-02-10 Thread David Pollak
Eric, You fixed it in 1.4.3-SNAPSHOT. Please let us know when you've upgraded 1.4.3 to release. Thanks, David On Mon, Feb 2, 2009 at 12:40 AM, etorreborre wrote: > > Hi David and Rickard, > > If you replace property(...) by Prop.forAll(...), the warnings should > disappear. > > On the other

Re: Fwd: [Lift] Cleaning up warnings

2009-02-02 Thread etorreborre
Hi David and Rickard, If you replace property(...) by Prop.forAll(...), the warnings should disappear. On the other hand I don't know why forAll(...) only doesn't work. Cheers, Eric. --~--~-~--~~~---~--~~ You received this message because you are subscribed to t

Re: Fwd: [Lift] Cleaning up warnings

2009-02-02 Thread Rickard Nilsson
It seems strange that forAll complains about getting a String => Boolean function. It works fine in the interpreter. The only reason I can see for that error message is that Scala somehow thinks that forAll is given two parameter lists. There exists an overloaded version of forAll of type [T](Gen[