Why does this have to be a menu? Why not add a macro to the test-engine code so that students can write (disable-tests)
On Nov 28, 2011, at 2:30 AM, Michael Sperber wrote: > > Robby Findler <ro...@eecs.northwestern.edu> writes: > >> [ moved to dev ] >> >> Apparently this broke somewhere in between v5.0 (June 2010) where it >> works and v5.1 (Feb 2011) where it doesn't. I can't use git bisect to >> find the precise commit because the earlier version doesn't compile on >> either my windows or my mac machine (mac is lion and windows uses too >> new of a version of visual studio). >> >> And I *hate* touching this code because something always ends up >> broken. I got really mad last time this code broke and so I hope we >> have better test suites now because of that, but I'm really not >> excited by the prospect of trying to change it again. Not only is the >> code hard to understand because it is poorly written, it is also >> unclear what parts of DrRacket it influences. >> >> Given all of this, my inclination is to simply remove this option. So >> far the only one who has spoken in favor of it gave a reason that >> (thankfully) no longer applies. >> >> Any objections? Comments? >> >> Mike? > > Some tests (especially check-property-based tests) are expensive, and > you don't always want to run them - especially with world/universe-based > code. Is there a way to have that option only with the student > languages? > > -- > Cheers =8-} Mike > Friede, Völkerverständigung und überhaupt blabla > _________________________________________________ > For list-related administrative tasks: > http://lists.racket-lang.org/listinfo/dev _________________________________________________ For list-related administrative tasks: http://lists.racket-lang.org/listinfo/dev
