Distribute config.c functionality across more modules
The config.c module and the or_options_t type are a layering problem: They initialize many other modules, and provide what amounts to a set of global variables for the configuration settings.
Instead, we could use the subsystems design to give modules the ability to declare and listen to various configuration options of their own, without requiring all the option handling to be in a single place.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information