Why are you using this crate?

[koivunej]

Over it's lifetime this crate has seen quite many downloads. For example, the 2021-10-19 had a huge (for this crate) 10k per day spike. I haven't used this crate myself in a few years but would be interested to know what are you using it for? If you are more than trying it out, does the duck typing aspect of $field.into_owned() give you any trouble, if so, how do you work around it?

I guess I'm mostly interested to hear if this should have some warning disclaimers on the README; I worry anyone trying this crate out quite quickly becomes aware of the limitations of it and the std::borrow::Cow. Would be happy to guide new folks to a blog post on std::borrow::Cow limitations if anyone knows a recent one.

[hoodie]

I personaly use it for some parsers where I try to create the entire data-structure only with cow types.

[neocturne]

My usecase also has to do with parsing.

After finishing my implementation, I've also found the crate https://crates.io/crates/ownable with similar features (even a few more I think, but for me this crate + my additions from #18 are sufficient).

ownable is a lot less popular than derive-into-owned according to crates.io's statistics, and neither see a lot of changes these days. If you are not using this crate yourself anymore, maybe it would make sense to recommend the other crate in your README? Would it make sense to switch my project over to ownable, rather than extending derive-into-owned?