Mutable options

[lmmx]

• Use TOML instead of dicts for options
• Use a singleton (i.e. a single parsed config) to [if I understand correctly?] permit mutable options (since if you modify the value in the module namespace, it will be modified in all imports of that module?)
  • I was given conflicting suggestions here, mainly to dissuade me from “code as config”, which I agree with but am still unsure whether mutating a parsed config will definitely persist across modules importing said parsed config

Proof of concept can be on top of the existing setup, so if it doesn’t work I can just try another approach...

• I still half suspect that mutating a class is more likely to persist across modules than mutating an instance of that class but I may be wrong

[lmmx]

Implemented TOML config parsing for mutable global config in 3e8b9fbd134fab90ab2023bed9bde02f2051f900