Add output_symbols
arg to codegen as performance mitigation
#361
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.
For complex expressions, the calculation of
Codegen.output_symbols
can grow quite large (encroaching on a minute or more). In some cases, the value ofoutput_symbols
can be specified externally. For example:output_symbols
readily available at the callsite (frequently it matches the input symbol set exactly).output_symbols
can be determined from anotherCodegen
object, for example in most (though not all) cases the following can work:Ideally
free_symbols
would be faster, but this is a mitigation/workaround that can offer worthwhile savings in some cases.This change adds an optional argument to the various constructors of
Codegen
so that the user can optionally provide the symbols themselves, and avoid an expensive computation.