-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Derive more for structs #544
Comments
@alexcrichton Is that an RFC as in the repo rust-lang/rfcs? I'll post on internals as a pre-RFC to get some thoughts together before I try to go down that road. I wanted to ask though, why do you think deriving |
Yeah in rust-lang/rfcs. I personally would be against such behavior as it doesn't make sense for most types and it also has serious compile-time implications. The very few niches which require it would end up imposing a cost on all other users by increasing the compile time of this crate (b/c of so many more impls) |
What about including it with #302, which I wasn't sure if you meant to suggest that earlier. |
Yes having it optional off-by-default is plausible, but I'd still want to measure the impact. |
I'd like to propose adding
#[derive(Copy, Debug, Eq, PartialEq)]
for some of the structs here in libc so they can be used downstream. This may be controversial for various reasons, but I have a specific use case forEq
andDebug
on thetermios
struct. AdditionallyClone
may be worth adding also, though I don't know if that could blanket apply to all structs.The text was updated successfully, but these errors were encountered: