[`windows-registry`] `set_multi_string` is hard to use

[justanotheranonymoususer]

Summary

Originally reported here: #3313

set_multi_string only accept[s] one generic type. This can make [it] hard to use, as it means the name and value need to use the same string type.

Not fixed for set_multi_string:

BTW, I didn't update set_multi_string's signature since it would break code which passed an empty array (with an inferred type), but, if windows-registry is about to have a major version bump, do you think the tradeoff would be worth it?

[Permik]

Can't you just call .into() on all values you pass to the fn so they get coerced to the correct value?

[justanotheranonymoususer]

I don't think so, not without heap allocation. Say I have &str for name, and Vec<String> for values. How would you do that?

[kennykerr]

I'm starting to think that the convenience/idiomatic crates that deal with strings should just use UTF-8 str and not provide all of the other options directly as it just complicates and confuses. Then for the cases where you absolutely need something else you can just use the APIs directly and write your own wrappers if needed.