The timing clause in the initial let is superfluous. Time doesn’t enter into the matching, which is really all that the template needs; if you need timings to deal with non-CliqueBot players differently, you can get them in the “do something else” section.
The idea behind the timing clause is so that the program will know precisely when it started running, rather than when the pattern-matching was completed. Now, I did this test:
> (define func (eval code0))
> (time (func code0))
cpu time: 0 real time: 1 gc time: 0
'C
which reveals that the difference isn’t significant. However, now that the code is out in the open, I’m not changing it.
The timing clause in the initial let is superfluous. Time doesn’t enter into the matching, which is really all that the template needs; if you need timings to deal with non-CliqueBot players differently, you can get them in the “do something else” section.
The idea behind the timing clause is so that the program will know precisely when it started running, rather than when the pattern-matching was completed. Now, I did this test:
which reveals that the difference isn’t significant. However, now that the code is out in the open, I’m not changing it.