-
Notifications
You must be signed in to change notification settings - Fork 1.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
A feature for types only #1560
Comments
I started working on this, but other things came in the way: #1286 |
I was actually thinking to also includes the flag types |
What problem are you trying to solve ? |
I'm mostly worried i'll accidentally use an |
Why can't you write a wrapper crate over libc that only re-exports what you want ? |
that might be an option. but even then i'll need to always check the types i'm re-exporting are still just typedefs(or structs?) but not a link. |
Sure, you'd have to do that. I personally do not think it is worth it to introduce complexity for this in the The libc crate does, however, have very strong backward compatibility guarantees, so we couldn't just remove this complexity later. |
That's fair. |
In the mean time you can just use the The issues related to that PR are more organizational than implementation-related. (I'm closing this, but please feel free to re-open if you think there is something else we can do here) |
Hi,
Would people be in favor of a feature for only types? i.e. no function definitions, just getting all the typedefs.
This can be useful for me here rust-lang/rfcs#2610 (comment)
Although I'm still debating if I should maintain my own list of typedefs for the kernel, flags etc.
How do people feel about this?
The text was updated successfully, but these errors were encountered: