[racket] Performance help

Sorry guys, I tried most of these (including profiler) and I should have
reported so as you could save your time. 

I did figure out of course that edits2 is the heavy in the program, 
the profiler points there. This isn't actionable advice, however. 

[With git we should be able to report all these attempts as commits
and undos but I really wish we had a better way of recording such a
tree of experiments (wasting New Year's days, argh).]

-- Matthias



On Jan 2, 2015, at 3:27 PM, Greg Hendershott <greghendershott at gmail.com> wrote:

>> Through the sophisticated profiling technique of commenting-out `or`
>> branches in `correct`
> 
> Oh, I should mention that I did try Optimization Coach, which is a
> wonderful tool!  It's given me many great suggestions.
> 
> In this case it could only suggest some inlines that didn't help. But
> for anyone who hasn't tried it, it's definitely worth running it.
> ____________________
>  Racket Users list:
>  http://lists.racket-lang.org/users