Re: [racket] Contracts on subclasses/mixins

2012-09-10 Thread Gregory Woodhouse
Thanks. That's important because I do override a few methods. For example, set-cell! erases pencil marks and clear-cell! puts them back in. But in most cases the methods are not overridden. Sent from my iPhone On Sep 10, 2012, at 1:23 PM, Asumu Takikawa wrote: > On 2012-09-10 12:35:52 -0700,

Re: [racket] Contracts on subclasses/mixins

2012-09-10 Thread Asumu Takikawa
On 2012-09-10 12:35:52 -0700, Gregory Woodhouse wrote: > Now, here's my question. provide grid% with its own contract-out > clause. It seems rather redundant (and presumably unnecessary) to > repeat the methods from base-grid% in the contract for grid%. You don't need to repeat the contracts unles

[racket] Contracts on subclasses/mixins

2012-09-10 Thread Gregory Woodhouse
I have a contract (define base-grid/c (class/c (given? (->m coord? coord? boolean?)) (get-cell (->m coord? coord? digit?)) (get-cell/given (->m coord? coord? (values digit? boolean?))) (set-cell! (->m coord? coord? digit? void?)) (set-given! (->m coord? coord? digit? void?)) (c