LARA

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
codefromscala [2007/08/16 14:13]
philippe.suter
codefromscala [2007/08/16 15:19]
philippe.suter
Line 7: Line 7:
   * use of match to define equals.   * use of match to define equals.
  
-==== From the libaries ​====+==== From the libraries ​====
  
 From ''​src/​library/​scala/​io/​BytePickle.scala''​. I was just wondering why the ''​Nil''​ case is not treated (and hence the need for ''​@unchecked''​). From ''​src/​library/​scala/​io/​BytePickle.scala''​. I was just wondering why the ''​Nil''​ case is not treated (and hence the need for ''​@unchecked''​).
Line 254: Line 254:
 [[http://​code.google.com/​p/​scalacheck/​|ScalaCheck]] is interesting for (almost) toy-sized examples. It uses almost exclusively sealed classes for pattern matching, and all its (6) source files compile without any warning. So it could be interesting as an example to show that our verifications are at least as good as scalac'​s. [[http://​code.google.com/​p/​scalacheck/​|ScalaCheck]] is interesting for (almost) toy-sized examples. It uses almost exclusively sealed classes for pattern matching, and all its (6) source files compile without any warning. So it could be interesting as an example to show that our verifications are at least as good as scalac'​s.
  
 +==== From sttracker ====
 +
 +([[http://​code.google.com/​p/​sttracker/​|sttracker]]) Nothing interesting there. Too small.