[racket-dev] Class contracts: opaque or transparent?

6 hours ago, Asumu Takikawa wrote:
> 
> The primary reason that I added opaque contracts is that they are
> needed for Typed Racket's eventual class/object support.

[If that's the motivation, then it sounds like these opaque contracts
are similar to TR forcing you to write types for all (toplevel)
defniitions, which it doesn't do.]

-- 
          ((lambda (x) (x x)) (lambda (x) (x x)))          Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!