Honestly I am not sure if this lazy init makes sense at all here as well, we have a hook for plugins to replace the entire set of flags, but that would fire prior to the initializer.
@roman any concerns with an eager init here? I guess the trivial fix is:
class << self
def flag_settings
...
end
end
flag_settings
I am thinking that the big reason this happened is that ruby does not ship a clean pattern for class initializers so it pushes devs towards inventing own/using lazy.