> Reproducible, and not related to optimization coach. I'm seeing this > too. It looks like a bad interaction between Planet2 installation in > DrRacket when "Populate Compiled Directories" is in effect. See: > > http://lists.racket-lang.org/users/archive/2013-February/056245.html
Something weird is happening: I'm seeing drracket-compiled files where I do _not_ expect to see them: --------------- slab:collects dyoo$ find . -name '*.zo' -print ./compatibility/compiled/drracket/errortrace/mlist_rkt.zo ./compatibility/compiled/drracket/errortrace/package_rkt.zo ./compatibility/compiled/drracket/mlist_rkt.zo ./compatibility/compiled/drracket/package_rkt.zo ./compiler/compiled/drracket/cm-accomplice_rkt.zo ./compiler/compiled/drracket/errortrace/cm-accomplice_rkt.zo ./compiler/private/compiled/drracket/errortrace/mach-o_rkt.zo ./compiler/private/compiled/drracket/errortrace/winutf16_rkt.zo ./compiler/private/compiled/drracket/mach-o_rkt.zo ./compiler/private/compiled/drracket/winutf16_rkt.zo ... --------------- Throughout the whole collects tree, I'm seeing that DrRacket has compiled many (if not all) the standard collections with DrRacket. That can't surely be right, right? _________________________ Racket Developers list: http://lists.racket-lang.org/dev
