The flag libraries I've used always make this easy, but the problem comes in when you try to reuse that dependency in another binary as a library.
Maybe you've seen a better flags library than I have, though.
Maybe you've seen a better flags library than I have, though.
When that came up what you'd do then is refactor that to be a class parameter or config option or whatever (and we'd usually ask that the flag be kept in some form).
Until then though you get the benefits of a quick and easy way to both expose and use tunables, which is much better than not having it at all.