Storing and re-storing rate-limit state?

[jcgruenhage]

I've got a usecase for which I need to store the state of the rate limit on disk when quitting the program, and restoring it when starting it again. What I'm currently considering is deriving Serialize and Deserialize on a bunch of the types in governor, and hiding that behind a serde feature flag. Do you think that makes sense to include here?

[Xevion]

If you could show some of the code, that'd help me replicate it. Also, if maintainers could look into making this a built-in feature, I'm sure others would enjoy it.