Setting Defaults Based on Primitive Config in `withConstructorDefault`
is it stretching the friendship with the new
withConstructorDefault to consider being able to eventually set defaults based on a primitive Config value?
