Yet again I wish the `cookie` crate would separate the signing feature to a different crate.
The first time it was mentioned, it was dismissed that being an optional feature should mean only those that opt-in would be affected. Turns out that's not true.
-
-
Mind if I ask a few more questions? In trust-dns we use features for disabling/enabling all signing/verifying (DNSSEC), these are all off by default. Is the way that the cookies lib has implemented this different in that it creates problems? Do we have a problem in trust-dns?
-
I think it's the general issue with features, namely that if a dependency enables a feature, the feature is enabled for every other crate in the dependency graph that depends on the crate with the feature. so, they have to be *strictly* additive
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.