pfernie

Thanks for the issue & PR! I am not sure the proposed behavior is consistent with [the spec](https://datatracker.ietf.org/doc/html/rfc6265#section-4.1.1). It states: ``` Servers SHOULD NOT include more than one Set-Cookie header...

I would also like to keep the implementation here simple, and not fall in the trap of trying to support "all use cases". But I do think there is a...

First of all, thanks for taking the time and effort to review and comment on these suggestions. In writing this up, a new issue occurred to me, which I opened...

The current naming scheme "restriction" is due to the fact I don't believe the metadata currently contains the timestamp (but maybe I overlooked it?). So, agreed, if that metadata were...

For my usage, reading the metadata for each name is fine (isn't costly), but it does seem some cases that might actually be undesirable. The existing behavior of the `prune`...

That makes sense. For my needs, perhaps a simpler flag to `gc` would suffice: `--echo-current-gen`. This would print the name of the remaining generation after a complete `gc` run. This...

This has obviously be dormant a while; in my particular case I've been simply not `gc`ing to avoid the "naming churn". Mainly because I did not have strong opinions on...

A new feature flag in `time` was introduced which (I believe) allows it to build w/ the `wasm` target. `cookie_store` has been updated to this version of `time`, and itself...

Thanks, that is a straightforward solution indeed!

Hi there! First, for clarity the `indexmap` dependency is only drawn in when the `preserve_order` feature of `cookie_store` is enabled. This enables the behavior that cookies are iterated in insertion...