Re: [racket-dev] Behavioral subtyping for editor<%> and its implementing classes

2010-12-07 Thread Matthew Flatt
Sounds fine. At Tue, 7 Dec 2010 15:20:54 -0500, Matthias Felleisen wrote: > > > If we take it out of editor<%>, we should not encounter any problems > whatsoever. It is possible that additional implements-interface checks will > succeed, but I am doubtful. Other than that I can't think of any

Re: [racket-dev] Behavioral subtyping for editor<%> and its implementing classes

2010-12-07 Thread Matthias Felleisen
If we take it out of editor<%>, we should not encounter any problems whatsoever. It is possible that additional implements-interface checks will succeed, but I am doubtful. Other than that I can't think of any problems. Should Asumu try and just run the whole test suite and if it works you co

Re: [racket-dev] Behavioral subtyping for editor<%> and its implementing classes

2010-12-07 Thread Matthew Flatt
I think the mismatch was not intentional. Maybe `do-copy' originally had a consistent interface, or maybe it was written down in `editor<%>' before it became apparent that its interface would be be specific to each different kin of editor. I can't think of any reason to have `do-copy' in its prese

[racket-dev] Behavioral subtyping for editor<%> and its implementing classes

2010-12-02 Thread Asumu Takikawa
Hi all, While writing contracts for classes in racket/gui, I noticed that the implementations of text% and pasteboard% do not act as behavioral subtypes of editor<%>, which both classes implement. In particular, consider the do-copy method from editor<%>. Its contract looks like this: (send an-e