UX/Design improvement

[aejenk]

Currently the crate works well - however its structure can leave a lot to be desired. The following are some problems:

• Mutations have a configure function to build their options up. Most of their contents is repeated, however there is no obvious way to group up the code - either as a macro, or into a seperate function.
• Currently, a range in the options requires a vector of 2 elements. If, however, an exact number is needed, there is no way to use a single element to represent that. Adding to the confusion, to pick an exact number, the maximum needs to be one more than the minimum, ex. [100,101].
• Add support for optional overrides for each mutation in the options.toml that would override the global settings.

[aejenk]

Currently, the options.toml file is being overhauled. Support for constants [5] and avoiding weird errors (panic when [100,100]), including support for local overrides. The problem here is that a significant amount of options are now Optional, and the derive macro does not currently support nested OVals, for example Option<Vec<isize>>.

This will require time, meaning this overhaul will take time to be added.

A benefit is that this may simplify the configure function.

[aejenk]

The update to the macro has been completed and seems to work perfectly fine. The configure function hasn't been simplified much, however since data validation has now moved into the bender.rs file instead, the functions have been generalised further.

An approach to replace with a macro should be attempted.

[aejenk]

A possible improvement could be to separate the Configuration from the Bender. This would simplify the bender greatly, while also reducing the cost of reconfiguring the bender each time, opting instead to pass a Configuration struct.