Run annotations separately for multiple comparators for measures that list them.
Generate more candidates.
Run any measure without a comparator once.
Backwards compatibility and cuts down on unnecessary overhead.
Each run needs to know the comparator being considered.
How best to do this?
Pass comparator id being considered to annotation setup()
Inject comparator @id into annotation environment variable.
Then comparator @id provides a way to get the identifier for the comparator.
The identifier of the comparator is the name of the variable or function that provides the value.
Passing @id of comparator into setup() lets it do the work of figuring out how to handle comparison values. Provide template annotations code that does this.
Run annotations separately for multiple comparators for measures that list them.
Generate more candidates.
Run any measure without a comparator once.
Backwards compatibility and cuts down on unnecessary overhead.
Each run needs to know the comparator being considered.
How best to do this?
@idinto annotation environment variable.@idprovides a way to get the identifier for the comparator.identifierof the comparator is the name of the variable or function that provides the value.Passing
@idof comparator intosetup()lets it do the work of figuring out how to handle comparison values. Provide template annotations code that does this.