about summary refs log tree commit diff
path: root/src/libcore/os.rs
AgeCommit message (Collapse)AuthorLines
2013-03-11core: formatting appeasementJeff Olson-3/+5
2013-03-11core: fix broken tests on windowsJeff Olson-3/+2
2013-03-11core: change import of exchange_alloc for win32 os::_list_dirJeff Olson-1/+1
2013-03-11rt/core: port os::list_dir to rust ref #4812Jeff Olson-8/+88
2013-03-11core: rt/core: impl os::env() in rust ref #4812Jeff Olson-8/+56
2013-03-11rt/core: impl os::getcwd() in rust ref #4812Jeff Olson-1/+8
2013-03-11librustc: Replace all uses of `fn()` with `&fn()`. rs=defunPatrick Walton-6/+6
2013-03-07test: Fix tests.Patrick Walton-2/+4
2013-03-07librustc: Convert all uses of `assert` over to `fail_unless!`Patrick Walton-43/+44
2013-03-07libcore: Remove `extern mod { ... }` from libcore. rs=deexterningPatrick Walton-11/+16
2013-03-06Add manual &self/ and &static/ and /&self declarations thatNiko Matsakis-26/+26
are currently inferred. New rules are coming that will require them to be explicit. All add some explicit self declarations.
2013-03-05auto merge of #5212 : thestinger/rust/iter, r=graydonbors-1/+1
A small step towards fixing #2827
2013-03-04Remove unused imports throughout src/Alex Crichton-2/+0
2013-03-03rustc: MIPS32 supportJyun-Yan You-0/+6
2013-03-03replace option::iter with a BaseIter implDaniel Micay-1/+1
2013-03-02auto merge of #5137 : yjh0502/rust/empty_struct, r=nikomatsakisbors-7/+11
The fix is straight-forward, but there are several changes while fixing the issue. 1) disallow `mut` keyword when making a new struct In code base, there are following code, ```rust struct Foo { mut a: int }; let a = Foo { mut a: 1 }; ``` This is because of structural record, which is deprecated corrently (see issue #3089) In structural record, `mut` keyword should be allowd to control mutability. But without structural record, we don't need to allow `mut` keyword while constructing struct. 2) disallow structural records in parser level This is related to 1). With structural records, there is an ambiguity between empty block and empty struct To solve the problem, I change parser to stop parsing structural records. I think this is not a problem, because structural records are not compiled already. Misc. issues There is an ambiguity between empty struct vs. empty match stmt. with following code, ```rust match x{} {} ``` Two interpretation is possible, which is listed blow ```rust match (x{}) {} // matching with newly-constructed empty struct (match x{}) {} // matching with empty enum(or struct) x // and then empty block ``` It seems that there is no such code in rust code base, but there is one test which uses empty match statement: https://github.com/mozilla/rust/blob/incoming/src/test/run-pass/issue-3037.rs All other cases could be distinguished with look-ahead, but this can't be. One possible solution is wrapping with parentheses when matching with an uninhabited type. ```rust enum what { } fn match_with_empty(x: what) -> ~str { match (x) { //use parentheses to remove the ambiguity } } ```
2013-03-02Remove REC, change related tests/docsJihyun Yu-7/+11
2013-03-01Rename core::private to core::unstable. #4743Brian Anderson-3/+2
2013-02-28Fix implicit leaks of imports throughout librariesAlex Crichton-10/+10
Also touch up use of 'pub' and move some tests around so the tested functions don't have to be 'pub'
2013-02-27libsyntax: Forbid mutable vectors. rs=demutingPatrick Walton-1/+1
2013-02-26auto merge of #5023 : mitsuhiko/rust/make-absolute-refactor, r=catamorphismbors-6/+2
This pull request moves the logic from os::make_absolute() into the path module and fixes path joining for Windows. It does this by adding an ``unsafe_join()`` function that implements the operating system's path joining semantics. Additionally it also adds an ``is_restricted()`` method to the trait which will return true if the path points to a windows device file.
2013-02-18core: Fix BSD breakage, I hopeTim Chevalier-0/+1
2013-02-18Refactored make_absolute into functionality on the PathArmin Ronacher-6/+2
2013-02-15attempt to fix BSD breakageGraydon Hoare-1/+1
2013-02-15auto merge of #4969 : nickdesaulniers/rust/issue3869, r=brsonbors-4/+7
Issue #3869 review? @nikomatsakis Convert all uses of vec::slice to vec::view Issue #3869 Rename const_view to const_slice Renamed mut_view to mut_slice Fix windows build error. `buf` is borrowed by the call to `as_mut_buf()` and so we must invoke `slice()` outside of that call.
2013-02-15Fix windows build error. `buf` is borrowed by the call toNiko Matsakis-4/+7
`as_mut_buf()` and so we must invoke `slice()` outside of that call.
2013-02-15libcore: Get rid of `move`.Luqman Aden-7/+7
2013-02-14libcore: replace mut_addr_of properly on macLuqman Aden-1/+2
2013-02-14libcore: Remove ptr::mut_addr_of since &mut is coerced to *mutLuqman Aden-9/+7
2013-02-14Remove all final references to die!Nick Desaulniers-2/+2
2013-02-13Remove die!, raplace invocations with fail! Issue #4524 pt 3Nick Desaulniers-1/+1
2013-02-13RIMOV core::vecBen Striegel-3/+3
Also remove as many uses as possible of vec::cast_to_mut and cast_from_mut
2013-02-11Long lines.Luqman Aden-2/+3
2013-02-11rt: remove last_os_error and adjust tests.Luqman Aden-1/+0
2013-02-11core: Rewrite last_os_error in Rust for windows as well.Luqman Aden-3/+33
2013-02-11core: Rewrite last_os_error in Rust for unix and provide access to errno ↵Luqman Aden-9/+103
(unix) and GetLastError (windows).
2013-02-07core: Remove structural records from the rest of core, except pipesTim Chevalier-8/+10
That will, sadly, require one more snapshot.
2013-02-07librustc: Lots of de-muting. rs=demutingPatrick Walton-4/+2
2013-02-07Make ~fn non-copyable, make &fn copyable, split barefn/closure types,Niko Matsakis-3/+0
correct handling of moves for struct-record update. Part of #3678. Fixes #2828, #3904, #4719.
2013-01-31Replace most invocations of fail keyword with die! macroNick Desaulniers-1/+1
2013-01-31core: Stamp out XXXes (comments only)Tim Chevalier-1/+1
2013-01-28core: Allow legacy records in in a few modulesTim Chevalier-0/+1
Because of macros, #[allow(structural_records]] in extfmt, gc, os, pipes, and run. Will need a snapshot.
2013-01-25Merge remote-tracking branch 'brson/nocommupstream'Brian Anderson-136/+68
Conflicts: src/libcore/private.rs src/libcore/task/mod.rs src/libcore/task/spawn.rs src/libstd/net_tcp.rs src/libstd/uv_global_loop.rs src/libstd/uv_iotask.rs
2013-01-24core: Mop up Windows breakageTim Chevalier-2/+2
2013-01-23core: Convert getenv/setenv to use a mutexBrian Anderson-136/+68
This much simpler implementation uses a global mutex and eliminates the kernel environment channel.
2013-01-23libsyntax: Remove `fn() unsafe { ... }`. r=graydonPatrick Walton-2/+4
2013-01-23core: Rename to_mut and from_mut to cast_to_mut and cast_from_mutTrinick-3/+3
2013-01-17Add a license check to tidy. #4018Brian Anderson-1/+1
2013-01-13Support ARM and Androidkyeongwoon-1/+13
Conflicts: src/libcore/os.rs src/librustc/back/link.rs src/librustc/driver/driver.rs src/librustc/metadata/loader.rs src/librustc/middle/trans/base.rs
2013-01-14core: Use libc::readlink function properlyTycho Sci-2/+11
The specification of readlink() says it's not guaranteed that the returned contents of the symbolic link is null-terminated.