core: Stabilize the mem module
Excluding the functions inherited from the cast module last week (with marked stability levels), these functions received the following treatment. * size_of - this method has become #[stable] * nonzero_size_of/nonzero_size_of_val - these methods have been removed * min_align_of - this method is now #[stable] * pref_align_of - this method has been renamed without the `pref_` prefix, and it is the "default alignment" now. This decision is in line with what clang does (see url linked in comment on function). This function is now #[stable]. * init - renamed to zeroed and marked #[stable] * uninit - marked #[stable] * move_val_init - renamed to overwrite and marked #[stable] * {from,to}_{be,le}{16,32,64} - all functions marked #[stable] * swap/replace/drop - marked #[stable] * size_of_val/min_align_of_val/align_of_val - these functions are marked #[unstable], but will continue to exist in some form. Concerns have been raised about their `_val` prefix. [breaking-change]
This commit is contained in:
parent
1ba7bd10c9
commit
19dc3b50bd
19 changed files with 223 additions and 138 deletions
|
@ -176,7 +176,7 @@ mod imp {
|
|||
if handle as uint == libc::INVALID_HANDLE_VALUE as uint {
|
||||
fail!("create file error: {}", os::last_os_error());
|
||||
}
|
||||
let mut overlapped: libc::OVERLAPPED = unsafe { mem::init() };
|
||||
let mut overlapped: libc::OVERLAPPED = unsafe { mem::zeroed() };
|
||||
let ret = unsafe {
|
||||
LockFileEx(handle, LOCKFILE_EXCLUSIVE_LOCK, 0, 100, 0,
|
||||
&mut overlapped)
|
||||
|
@ -192,7 +192,7 @@ mod imp {
|
|||
|
||||
impl Drop for Lock {
|
||||
fn drop(&mut self) {
|
||||
let mut overlapped: libc::OVERLAPPED = unsafe { mem::init() };
|
||||
let mut overlapped: libc::OVERLAPPED = unsafe { mem::zeroed() };
|
||||
unsafe {
|
||||
UnlockFileEx(self.handle, 0, 100, 0, &mut overlapped);
|
||||
libc::CloseHandle(self.handle);
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue