tag:blogger.com,1999:blog-5336273.post8896556443387913756..comments2023-08-23T21:56:42.999+09:00Comments on A++ [Eric Torreborre's Blog]: Better unit tests with ScalaCheck (and specs)Unknownnoreply@blogger.comBlogger3125tag:blogger.com,1999:blog-5336273.post-15597344106844541822008-01-21T14:40:00.000+09:002008-01-21T14:40:00.000+09:00Done!Homepage: http://groups.google.com/grou...Done!<BR/><BR/>Homepage: http://groups.google.com/group/specs-users<BR/>Group email: specs-users@googlegroups.com<BR/><BR/>Waiting for you on the mailing-list!<BR/><BR/>Eric.Erichttps://www.blogger.com/profile/16484514586929815703noreply@blogger.comtag:blogger.com,1999:blog-5336273.post-6932633313733662662008-01-21T08:24:00.000+09:002008-01-21T08:24:00.000+09:00You should probably have a mailing list for specs....You should probably have a mailing list for specs. I am using specs in my project and often stumble on few problems.gnufiedhttps://www.blogger.com/profile/09306567017030452841noreply@blogger.comtag:blogger.com,1999:blog-5336273.post-48402780457115536762008-01-16T23:19:00.000+09:002008-01-16T23:19:00.000+09:00In an upcoming ScalaCheck release, you can write y...In an upcoming ScalaCheck release, you can write your implicit genCan function like this instead:<BR/><BR/>implicit def genCan[T <: Arbitrary[T]]: Arbitrary[Can[T]] = ...<BR/><BR/>This is because the type inferencer was improved in Scala 2.6.1. However, I still lack a feature (Scala ticket #298), for making it perfect, so I haven't introduced the change yet.<BR/><BR/> / Rickardrickynilshttps://www.blogger.com/profile/09000442010513234623noreply@blogger.com