On Fri, May 22, 2015 at 5:41 PM, Atticus <attic...@posteo.org> wrote:
> > Imho it would be nice if there was a small hint in the documentation > about that case, perhaps there is and I didn't see it? Yes, there is : http://docs.racket-lang.org/style/Units_of_Code.html?q=define%2Fcontract#%28part._.Contracts%29 In practice, I design tests in a system level abstraction. black-box tests are always embedded in documentation so that if the documentation does not show errors, then the system is reasonably correct (for bugs that already found). source code can keep elegant, and leave all the dirty things to scribble. I almost do not write white-box tests since Racket and Typed Racket itself has already formal enough, moreover these tests or verifications can also be moved to documentation if needed. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
