On Tue, Feb 26, 2013 at 2:23 AM, Norman Gray <[email protected]> wrote: > > Sam, hello. > > On 2013 Feb 26, at 05:42, Sam Tobin-Hochstadt wrote: > >> This is, sadly, a known problem with Racket, Typed Racket, and >> submodules, which Matthew doesn't think there's much hope of fixing >> without major surgery on the expander. So for now you'll need to >> write your test cases in a separate module. > > I've found that workaround. Is there any way that, while avoiding major > surgery, rackunit or the expander could detect it's in this situation and > emit a less perplexing error message?
Unfortunately, I don't know of a way to do this. > I imagine this is also the reason why rackunit, when running with typed > Racket, reports generated names for mismatched values, rather than the actual > variables used in the check-* tests. It makes locating the failed test a > little more roundabout than it might be. No, that isn't the same issue. I'll look at why that happens. Sam > -- > Norman Gray : http://nxg.me.uk > SUPA School of Physics and Astronomy, University of Glasgow, UK > ____________________ Racket Users list: http://lists.racket-lang.org/users
