- 30 6月, 2018 14 次提交
-
-
由 Oliver Schneider 提交于
-
由 bors 提交于
hygiene: Implement transparent marks and use them for call-site hygiene in proc-macros Fixes https://github.com/rust-lang/rust/issues/50050
-
由 bors 提交于
Lowering cleanups [1/N]
-
由 bors 提交于
Implement PartialEq between &str and OsString This fixes #49854. It allows equality comparison between `OsString` values and `str` references, such as `os_string == "something"`.
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
`$crate` is not resolved at def-site of a macro, but rather at "transitive def-site"
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
-
由 bors 提交于
Fix incorrect type mismatch label pointing at return type CC #46302.
-
由 Esteban Küber 提交于
-
由 bors 提交于
Make the public API of the alloc crate a subset of std This only affects **unstable** APIs. I plan to submit an RFC proposing to stabilize the crate. The reason it isn’t stable yet (https://github.com/rust-lang/rust/issues/27783) is in case we end up merging the standard library crates into one. However the `core` crate is already stable, so if that happens we’ll need to keep it working somehow (likely by making replacing its contents by `pub use` items). We can do the same for `alloc`. This PR will hopefully make this easier, but even if that doesn’t happen consistency with `std` seems good.
-
- 29 6月, 2018 26 次提交
-
-
由 bors 提交于
Update LLVM to 1c817c7a0c828b8fc8e8e462afbe5db41c7052d1 https://github.com/rust-lang/llvm/pull/118 https://github.com/rust-lang/llvm/pull/119
-
由 bors 提交于
[NLL] Better move errors Make a number of changes to improve the quality of NLL cannot move errors. * Group errors that occur in the same `match` with the same cause. * Suggest `ref`, `&` or removing `*` to avoid the move. * Show the place being matched on. Differences from AST borrowck: * `&` is suggested over `ref` when matching on a place that can't be moved from. * Removing `*` is suggested instead of adding `&` when applicable. * Sub-pattern spans aren't used, this would probably need Spans on Places. Closes #45699 Closes #46627 Closes #51187 Closes #51189 r? @pnkfelix
-
由 Simon Sapin 提交于
-
由 Simon Sapin 提交于
-
由 Simon Sapin 提交于
… since `std` has no corresponding reexports. Use `alloc::vec::Vec` and `alloc::string::String` instead.
-
由 Simon Sapin 提交于
-
由 Simon Sapin 提交于
This matches std::collections
-
由 Simon Sapin 提交于
-
由 Simon Sapin 提交于
-
由 Gabriel Majeri 提交于
-
由 Gabriel Majeri 提交于
-
由 Gabriel Majeri 提交于
Allows for example `os_string == "something"`
-
由 bors 提交于
Add a fallback for stacktrace printing for older Windows versions. Some time ago we switched stack inspection functions of dbghelp.dll to their newer alternatives that also capture inlined context. Unfortunately, said new alternatives are not present in older dbghelp.dll versions. In particular Windows 7 at the time of writing has dbghelp.dll version 6.1.7601 from 2010, that lacks StackWalkEx and friends. Tested on my Windows 7 - both msvc and gnu versions produce a readable stacktrace. Fixes #50138
-
由 bors 提交于
park/park_timeout: prohibit spurious wakeups in next park <pre><code> // The implementation currently uses the trivial strategy of a Mutex+Condvar // with wakeup flag, which does not actually allow spurious wakeups. </pre></code> Because does not actually allow spurious wakeups. so we have let thread.inner.cvar.wait(m) in the loop to prohibit spurious wakeups. but if notified after we locked, this notification doesn't be consumed, it return, the next park will consume this notification...this is also 'spurious wakeup' case, 'one unpark() wakeups two park()'. We should improve this situation: `thread.inner.state.store(EMPTY, SeqCst);`
-
由 bors 提交于
Arc: remove unused allocation from Weak::new() It seems non-obvious that calling `Weak::new()` actually allocates space for the entire size of `T`, even though you can **never** access that data from such a constructed weak pointer. Besides that, if someone were to create many `Weak:new()`s, they could be unknowingly wasting a bunch of memory. This change makes it so that `Weak::new()` allocates no memory at all. Instead, it is created with a null pointer. The only things done with a `Weak` are trying to upgrade, cloning, and dropping, meaning there are very few places that the code actually needs to check if the pointer is null.
-
由 bors 提交于
Fix macro missing from doc search Fixes #51095. r? @QuietMisdreavus
-
由 bors 提交于
Rollup of 6 pull requests Successful merges: - #51636 (Refactor error reporting of constants) - #51765 (Use assert_eq! in copy_from_slice) - #51822 (Provide existing ref suggestions for more E0308 errors) - #51839 (Detect overflows of non u32 shifts) - #51868 (Remove process::id from 'Stabilized APIs' in 1.27.0 release notes) - #51875 (Explicitely disable WASM code generation for Emscripten) Failed merges: r? @ghost
-
由 Mark Rousskov 提交于
Explicitely disable WASM code generation for Emscripten Emscripten changed the default behavior recently: https://github.com/kripken/emscripten/blob/bd050e64bb0d9952df1344b8ea9356252328ad83/ChangeLog.markdown#v1381-05172018 It now defaults to WebAssembly and requires an explicit flag to generate asm.js. WASM=0 is also valid for older emcc and thus doesn't break it.
-
由 Mark Rousskov 提交于
Remove process::id from 'Stabilized APIs' in 1.27.0 release notes process::id was already stabilized in 1.26.0 and is marked as such in the docs.
-
由 Mark Rousskov 提交于
Detect overflows of non u32 shifts
-
由 Mark Rousskov 提交于
Provide existing ref suggestions for more E0308 errors
-
由 Mark Rousskov 提交于
Use assert_eq! in copy_from_slice This will print both lengths when the assertion fails instead of just saying that they're different. Output of current stable and nightly (modulo the exact line number): ``` thread 'main' panicked at 'destination and source slices have different lengths', libcore/slice/mod.rs:1645:9 ``` Output after this PR: ``` thread 'main' panicked at 'assertion failed: `(left == right)` left: `123`, right: `456`: destination and source slices have different lengths', libcore/slice/mod.rs:1645:9 ``` Note that I have not run the tests locally.
-
由 Mark Rousskov 提交于
Refactor error reporting of constants cc @EddyB This PR should not change any behaviour. It solely simplifies the internal handling of the errors
-
由 moxian 提交于
-
由 moxian 提交于
-