| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
| |
An issue with scalacheck and actors where an excess of thread pools gets created - tmp fix. No review.
|
| |
|
|
|
|
|
|
|
|
|
| |
including "CheckEither", written against scalacheck 1.2 in the year 471
AD. Removed all the duplicates I could find, mostly between pending
and files. Renamed a bunch of tests so they wouldn't look like likely
duplicates next time around. Nominated somebody else to do this once in
a while.
No review.
|
| |
|
|
|
|
| |
Disabled scalacheck tests because they interfere with library
refactorings (refactorings break scalacheck).
|
| |
|
|
|
|
| |
Unique's seeming victory is overruled by committee. It is "distinct",
not "unique", wherein lies the nub. No review.
|
| |
|
|
|
|
|
|
|
| |
Striking while the iron is hot, renamed removeDuplicates to unique and
deprecated removeDuplicates. The debate between distinct and unique was
vigorous but unique won by a freckle. (Dark horse 'nub' was disqualified
for taking performance enhancers.) The only thing which might need
review is the choice of name, but review by odersky.
|
| |
|
|
|
|
|
| |
Added some more scalacheck tests to list, incidentally inspiring
millions of commit log readers to say out loud "hey, I could be writing
tests like those!"
|
| |
|
|
|
|
| |
The first working scalacheck test! Now Arbitrary is working for us
instead of our nemesis Capt. Entropy.
|
| | |
|
| |
|
