Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Create a separate libc_types crate for basic C types #1783

Closed
wants to merge 4 commits into from
Closed

Create a separate libc_types crate for basic C types #1783

Changes from 1 commit
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b322ac2
Create a separate libc_types crate for basic C types
Amanieu Nov 3, 2016
ef4e3bc
Fix quote from GCC documentation
Amanieu Nov 3, 2016
55ee184
Update motivation and drawbacks
Amanieu Nov 3, 2016
85b7d3e
Add c_char
Amanieu Nov 4, 2016
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Add c_char
  • Loading branch information
@Amanieu
Amanieu authored Nov 4, 2016
commit 85b7d3e990f3ad33b3f9dbd2b68080e712fab169
2 changes: 2 additions & 0 deletions text/0000-libc-types.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -65,6 +65,8 @@ pub type ssize_t;

pub type c_long;
pub type c_ulong;

pub type c_char;
```

To preserve backward compatibility, these types will be re-exported by the `libc` crate. This is not a breaking change since the `c_void` type still only comes from a single source, so there will not be conflicting definitions. Thus only a minor version bump is required, which avoids extensive breakage across the ecosystem similar to what happened when the `libc` version was bumped to 0.2.
Expand Down