Some annotation functions require a one time calculation that is then re-used for each performer. An example of this is achievable benchmark. It requires the data from all the performers, and would have to be re-calculated if it were a function call that couldn't store the result.
Implement and test support for a convention to call a function setup_cache that returns a list which will be then added to the annotation environment as the cache variable.
No-op if the sourced annotations do not provide a setup_cache function.
Some annotation functions require a one time calculation that is then re-used for each performer. An example of this is achievable benchmark. It requires the data from all the performers, and would have to be re-calculated if it were a function call that couldn't store the result.
Implement and test support for a convention to call a function
setup_cachethat returns a list which will be then added to the annotation environment as thecachevariable.No-op if the sourced annotations do not provide a
setup_cachefunction.