No, they are different algorithm hence the change, even if we use the same multipliers and weight in the generic `@Mod10Check` it wouldn't have the same result as `@LuhnCheck`, 

`@LuhnCheck` ain't just a variant, there isn't a generic version of it, because of that it ignores all the `@Mod10Check` specific options, that is the reason to separate them, sure we could just create an option on the old constraint but that would cause the same problem that the old `@ModCheck` had too many options ignored for nothing.

After some research I found the most used options are `multiplier=3` and `weight=1`, so I changed the default values to reflected that and the test to make easier to get real codes.