<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jun 27, 2013 at 10:08 PM, Sam Tobin-Hochstadt <span dir="ltr"><<a href="mailto:samth@ccs.neu.edu" target="_blank">samth@ccs.neu.edu</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Thu, Jun 27, 2013 at 11:06 PM, Robby Findler<br> <<a href="mailto:robby@eecs.northwestern.edu">robby@eecs.northwestern.edu</a>> wrote:<br> > One fairly clear thing is that the mzlib manual can move into the<br> > compatibility-lib.<br> <br> </div>I agree.<br> <div class="im"><br> > We could move the mzlib-specific files from (the collection) tests/racket<br> > into a new tests/mzlib and put that into the compatibility-lib.<br> ><br> > But that probably requires actual adjustments because tests/racket is<br> > load-based ...<br> ><br> > Probably all of the mzlib-specific tests could be made to run in a #lang<br> > context without too much trouble, tho.<br> <br> </div>I don't feel 100% confident mucking with the tests/racket<br> infrastructure, and I don't know how worth it this would be.<br> <br> BTW, you have some commented-out tests in racket/private/contract that<br> `(require mzlib/contract)`.<br> <span class="HOEnZb"><font color="#888888"><br><br></font></span></blockquote><div><br></div><div style>I know. Is that a problem?</div><div style><br></div><div style>Robby </div></div><br></div></div>