diff options
| author | bors <bors@rust-lang.org> | 2015-04-14 00:07:50 +0000 |
|---|---|---|
| committer | bors <bors@rust-lang.org> | 2015-04-14 00:07:50 +0000 |
| commit | e6a812402828f0f11b0de7a7e0c08c1d85a437f1 (patch) | |
| tree | f2570188dcccb4c7c362ae047e3411fa1e1baa1c /src/libstd/sys/unix/stack_overflow.rs | |
| parent | f55e66aaed42589dcda0221a4545dbaaec68e577 (diff) | |
| parent | 2705051e2067e8f467b4cb9bc75e801a5cd4f0e7 (diff) | |
| download | rust-e6a812402828f0f11b0de7a7e0c08c1d85a437f1.tar.gz rust-e6a812402828f0f11b0de7a7e0c08c1d85a437f1.zip | |
Auto merge of #24251 - alexcrichton:unsafe-from-raw-fd, r=aturon
As pointed out in [RFC issue 1043][rfc] it is quite useful to have the standard I/O types to provide the contract that they are the sole owner of the underlying object they represent. This guarantee enables writing safe interfaces like the `MemoryMap` API sketched out in that issue. [rfc]: https://github.com/rust-lang/rfcs/issues/1043 As constructing objects from these raw handles may end up violating these ownership gurantees, the functions for construction are now marked unsafe. [breaking-change] Closes rust-lang/rfcs#1043
Diffstat (limited to 'src/libstd/sys/unix/stack_overflow.rs')
0 files changed, 0 insertions, 0 deletions