My students have found it on their own, and they're using it for things like "last". I have no problem slapping them on the wrist for that, but that's a separate issue. I just wanted to be able to explain to them why struct comparisons are suddenly broken.
- Adam
> On Nov 5, 2011, at 9:03 AM, Robby Findler wrote:
>>> (require racket) generally doesn't work in the teaching languages. It
>> shadows define-struct, in this case, and you get the wrong version (so
>> you get generative structs).
>>>> Why are you doing (require racket)? There's probably some smaller
>> library you could use that would not shadow core things...
>>>> Robby
>>>> On Sat, Nov 5, 2011 at 8:54 AM, Adam Shaw <adamshaw at cs.uchicago.edu> wrote:
>>> Hi --
>>> My students noticed that certain check-expect tests stop working in the
>>> presence of (require racket). For example, the check-expect in this
>>> three-line file fails under ISλ:
>>> (require racket)
>>> (define-struct foo (x))
>>> (check-expect (make-foo 0) (make-foo 0))
>>> Why is this happening?
>>> Thanks -- Adam
>>> _________________________________________________
>>> For list-related administrative tasks:
>>>http://lists.racket-lang.org/listinfo/users>>>>>>