- 24 2月, 2015 28 次提交
-
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
This test appears to pass cleanly on master. Closes #13361
-
由 Manish Goregaokar 提交于
We already do this for the function arguments, but miss it for the retslot pointer, which can lead to LLVM assertions because the retslot has the wrong type. Fixes #22663
-
由 Manish Goregaokar 提交于
Leading hyphens already don't work (#22661), so no code should break from this change. Closes #22661.
-
由 Manish Goregaokar 提交于
We can't call into the inner reader for a 0-byte read because that may end up blocking or returning an error. r? @alexcrichton
-
由 Manish Goregaokar 提交于
e. g. ``` let b: Box<Foo> = Box::from_raw(p); ``` instead of ``` let b: Box<Foo> = mem::transmute(p); ``` Patch also changes closure release code in `src/libstd/sys/unix/thread.rs` when `pthread_create` failed. Raw pointer was transmuted to box of `FnOnce()` instead of `Thunk`. This code was probably never executed, because `pthread_create` rarely fails. (And there are two more patches in PR: fix typo in doc and mark `from_raw` and `into_raw` functions inline.)
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
r? @huonw
-
由 Manish Goregaokar 提交于
"body": null,
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
- Various grammatical changes. - Use triple-backtick syntax and `sh` highlighting for code blocks. - Fix indentation of code block in step 2 of \"Building on Windows\". - Use title case for \"Getting Help\" subheading.
-
由 Manish Goregaokar 提交于
The Rust Reference should include the tuple indexing (using a number as a field) notation; currently it is only available on http://doc.rust-lang.org/std/primitive.tuple.html and not easily searchable.
-
由 Manish Goregaokar 提交于
fix issue #22535
-
由 Manish Goregaokar 提交于
Update from straight line to reference-style link.
-
由 Manish Goregaokar 提交于
It looks like a few spots in the documentation were missed when renaming `Bitv` and `BitvSet`. This fixes the docs to use their current names.
-
由 Manish Goregaokar 提交于
r? @huonw
-
由 Manish Goregaokar 提交于
r? @steveklabnik I've updated the iterators chapter to reflect the fact that you can now iterate over `for` loops without calling `.iter()`.
-
由 Manish Goregaokar 提交于
r? @steveklabnik
-
由 Manish Goregaokar 提交于
r? @steveklabnik
-
由 Manish Goregaokar 提交于
And minor fixes to other docs. r? @nikomatsakis
-
由 Manish Goregaokar 提交于
Clarify that `to_string` is how you make `String`. Use a coercion in an example. r? @steveklabnik
-
由 Manish Goregaokar 提交于
Fixed example threaded code in intro doc never printing results. Threads were created with Thread::spawn instead of Thread::scoped. Also added correct thread handling like in the first example of the document.
-
由 Manish Goregaokar 提交于
-
由 Manish Goregaokar 提交于
-
- 23 2月, 2015 12 次提交
-
-
由 Manish Goregaokar 提交于
This is a patch for #17829. In `compiletest` there are multiple layers which capture the output. The first layer is `run_tests_console` which is used to execute all tests. Then there are some tests that contain unit tests, which by default also captures output. Therefore `compiletest` adds `RUST_TEST_NOCAPTURE` (and `RUST_TEST_TASKS` for completeness) to the run environment of the task. Finally, the task used to execute a test redirects stdout and stdin. At the moment, the `VERBOSE=1` prints all captured output of the task (but has to print stdout and stderr separately). So at the moment using `RUST_TEST_NOCAPTURE=1` only makes sense when also using `VERBOSE=1` which seems a little bit cumbersome. Should I update the patch to only print the output of the tasks that actually execute the test (`VERBOSE=1` includes other stuff, like the output of the task used to compile the test)? This will probably involve adding an extra flag to some functions in `src/compiletest/runtest.rs` to distinguish compilation runs from runs that execute the actual tests.
-
由 Manish Goregaokar 提交于
Fixes #22152
-
由 bors 提交于
Please see discussion in #19284 .
-
由 Alexander Bliskovsky 提交于
-
由 Alexander Bliskovsky 提交于
-
由 Stepan Koltsov 提交于
... to convert between Box and raw pointers. E. g. use ``` let b: Box<Foo> = Box::from_raw(p); ``` instead of ``` let b: Box<Foo> = mem::transmute(p); ``` Patch also changes closure release code in `src/libstd/sys/unix/thread.rs` when `pthread_create` failed. Raw pointer was transmuted to box of `FnOnce()` instead of `Thunk`. This code was probably never executed, because `pthread_create` rarely fails in practice.
-
由 Stepan Koltsov 提交于
-
由 Tshepang Lekhonkhobe 提交于
-
由 Stepan Koltsov 提交于
-
由 Nick Cameron 提交于
-
由 bors 提交于
This is not a complete implementation of the RFC: - only existing methods got updated, no new ones added - doc comments are not extensive enough yet - optimizations got lost and need to be reimplemented See https://github.com/rust-lang/rfcs/pull/528 Technically a [breaking-change]
-
由 Tshepang Lekhonkhobe 提交于
-