-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement ToOwned
instead of having a custom to_owned
method
#286
Comments
Additionally, |
I don’t really care, so I’m not gonna implement this myself. If someone wants to send a PR I’ll take it. |
@SimonSapin I will do that in a bit. I think that it doesn't make sense to close an issue like this if it's desired but not prioritised; it's a decent first bug for someone who wants to submit a PR. |
It’s not. I don’t see the point. I’m only not opposed to it enough to reject a PR if someone else wants it enough to make a PR. |
I see that this is linked from an issue on Clippy, which tends to be very opinionated. I’d be much less sympathetic accepting code that I’ll need to maintain if it’s based purely on an opinion of how things should be in principle, rather than on someone’s concrete use case who will then actually use that code. |
A very simple use case is storing As far as the actual It does have feasible use cases, but I figured I'd just open an issue now because I'm focused on something else at the moment and didn't want to forget about it. I'll offer a PR tomorrow. :) |
Ah, mentioning To some extent, the only reason I created the |
No description provided.
The text was updated successfully, but these errors were encountered: