We currently have compiler run interpolation support, but only for the ${time} variable, which expands to the UNIX timestamp when the compiler was configured.
This issue tracks adding a ${mutant} variable, which tracks the Mutation.Selection variable in the plan (if it exists). This variable will eventually be stepped upwards by the mutation test runtime, and so will be the correct thing to set C4_MUTATION to when mutating.
While I'm at it, it's probably a good idea to rename ${time} to something more indicative, like ${config_time}.
We currently have compiler run interpolation support, but only for the
${time}variable, which expands to the UNIX timestamp when the compiler was configured.This issue tracks adding a
${mutant}variable, which tracks theMutation.Selectionvariable in the plan (if it exists). This variable will eventually be stepped upwards by the mutation test runtime, and so will be the correct thing to setC4_MUTATIONto when mutating.While I'm at it, it's probably a good idea to rename
${time}to something more indicative, like${config_time}.