Avoid re-making the DCT table if it is already correct when initialising #241
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is the one remaining change from #172 that was not effectively integrated.
I will need to find a patch that demonstrates the speed issue to see if this is a worthwhile optimisation, but it also needs checking for anything that uses DCT. The behaviour to check is that around anything that causes an object to have init() called (so does the object produce the correct results on a second analysis for example)