Closed bartelink closed 5 years ago
@szer is 8ae2f95 a good idea? Its obviously a potentially breaking change, but should be easy enough to adapt to?
I know it's an extra alloc and the impl is ugly. But I can't think of a cleaner way to align with the way that the 1.2 interface has a new IDictionary<string,string>
overload
Wait - I'll support both and call the new one config
so it matches exactly, doh!
I think it's an easy thing to adapt to for sure. Seq of value pairs to dictionary seems like a natural conversion.
Extra allocation is fine because you couldn't preallocate shared instance of empty mutable(!) dictionary.
Sorry, I edited my comment :shame: - I found a better way which is to give it a new name which matches the equivalent CK arg.
config
optional arg on config ctors to align with CK API's newIDictionayr<string,string>
overload