Dave Mitchell wrote: > I want to discuss some modest proposals for better testing of performance > and optimisations. The first four suggestions are simple, concrete, and (I > hope) non-controversial. The fifth is more woolly and up for discussion. What you propose all sounds good to me, but please consider the following: As you can see, I recently added t/op/opt.t, because I was tired of tweaking B::Concise expected output and because simple optimisations have been broken in the past. How would that fit into your scheme? Should we just move it to t/perf and just give it a more descriptive name? Also, another broken optimisation that comes to mind is in-place lc and uc, which we currently have no way to test. Would it be a good idea to add a test file that uses -D output to test optimisations (and add some -D output for in-place lc)? There is one that tests regexp compilation like that already, though I don't remember its name.Thread Previous | Thread Next