[racket-dev] chaperones in 5.3.1?

On Tue, Oct 23, 2012 at 9:42 PM, Robby Findler
<robby at eecs.northwestern.edu> wrote:
> Is it possible that one of those vectors is mutable and the other is immutable?

I'm not sure yet.  Sorry about not replying immediately; I'm still
trying to figure out where the error is occurring.  It's at a contract
boundary as far as I can tell.  I got a slightly better error trace
now:


------
prop:chaperone-contract: expected a chaperone of
'#("#<path:/Users/dyoo/work/whalesong/tests/more-tests/js-binding.rkt>"
401 14 10 9), got
'#("#<path:/Users/dyoo/work/whalesong/tests/more-tests/js-binding.rkt>"
401 14 10 9)
  context...:
   /Users/dyoo/local/racket/collects/racket/contract/private/prop.rkt:233:10
   /Users/dyoo/local/racket/collects/racket/contract/private/prop.rkt:233:10
   /Users/dyoo/work/whalesong/compiler/compiler.rkt:124:0: compile
   /Users/dyoo/work/whalesong/compiler/compiler.rkt:1924:2: in-other-context
   /Users/dyoo/work/whalesong/compiler/compiler.rkt:124:0: compile
   /Users/dyoo/work/whalesong/compiler/compiler.rkt:124:0: compile
   /Users/dyoo/work/whalesong/compiler/compiler.rkt:772:0: compile-lambda-body
   /Users/dyoo/work/whalesong/compiler/compiler.rkt:44:0: -compile
   ...
--------------

I'm hacking into Whalesong to see if I can nail this down more precisely.