diff options
| author | bors <bors@rust-lang.org> | 2015-10-06 01:26:13 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-10-06 01:26:13 +0000 |
| commit | 88b6a5063df6e52921cbbb99940a38bebdcd6749 (patch) | |
| tree | 0edf69160140765be3273d47c13eca15cabfc81f /src/libstd/sys/unix/stack_overflow.rs | |
| parent | 32a8567ea4ded47ac4cfd39bc808bb8d6f2e119c (diff) | |
| parent | bd6758a2b5781599d1e4eb48a897616d1b0cf8a0 (diff) | |
| download | rust-88b6a5063df6e52921cbbb99940a38bebdcd6749.tar.gz rust-88b6a5063df6e52921cbbb99940a38bebdcd6749.zip | |
Auto merge of #28779 - alexcrichton:ffi-isize-usize, r=nrc
This lint warning was originally intended to help against misuse of the old Rust `int` and `uint` types in FFI bindings where the Rust `int` was not equal to the C `int`. This confusion no longer exists (as Rust's types are now `isize` and `usize`), and as a result the need for this lint has become much less over time. Additionally, starting with [the RFC for libc][rfc] it's likely that `isize` and `usize` will be quite common in FFI bindings (e.g. they're the definition of `size_t` and `ssize_t` on many platforms). [rfc]: https://github.com/rust-lang/rfcs/pull/1291 This commit disables these lints to instead consider `isize` and `usize` valid types to have in FFI signatures.
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions
