- 28 4月, 2020 9 次提交
-
-
由 bors 提交于
Rollup of 7 pull requests Successful merges: - #67841 (Add Read/Write::can_read/write_vectored) - #71524 (Minimize parameter of coerce_borrowed_pointer()) - #71558 (Cleanup and document `-Z tls-model` ) - #71578 (linkchecker: fix typo in main.rs) - #71596 (Fix broken link in `QPath` documentation) - #71604 (make recursive-zst test unleashed) - #71605 (No need to whitelist E0750 anymore) Failed merges: r? @ghost
-
由 Dylan DPC 提交于
No need to whitelist E0750 anymore Since #71304 has been fixed, no need to whitelist it anymore. r? @Dylan-DPC
-
由 Dylan DPC 提交于
make recursive-zst test unleashed Make sure we find this issue even without const qualification. r? @oli-obk @ecstatic-morse
-
由 Dylan DPC 提交于
Fix broken link in `QPath` documentation r? @Dylan-DPC
-
由 Dylan DPC 提交于
linkchecker: fix typo in main.rs Came across this while reading the file.
-
由 Dylan DPC 提交于
Cleanup and document `-Z tls-model` r? @Amanieu
-
由 Dylan DPC 提交于
Minimize parameter of coerce_borrowed_pointer() Change last parameter of `coerce_borrowed_pointer()` from `TypeAndMut` to `Mutability` (similar to `coerce_unsafe_ptr()`), since the `TypeAndMut::ty` is never used directly in this function.
-
由 Dylan DPC 提交于
Add Read/Write::can_read/write_vectored When working with an arbitrary reader or writer, code that uses vectored operations may end up being slower than code that copies into a single buffer when the underlying reader or writer doesn't actually support vectored operations. These new methods allow you to ask the reader or witer up front if vectored operations are efficiently supported. Currently, you have to use some heuristics to guess by e.g. checking if the read or write only accessed the first buffer. Hyper is one concrete example of a library that has to do this dynamically: https://github.com/hyperium/hyper/blob/0eaf304644a396895a4ce1f0146e596640bb666a/src/proto/h1/io.rs#L582-L594
-
由 bors 提交于
Emit basic block info for stmts and terminators in MIR dumps only with -Zverbose r? @EddyB as per https://github.com/rust-lang/rust/pull/70755#discussion_r403419476
-
- 27 4月, 2020 28 次提交
-
-
由 Oliver Scherer 提交于
-
由 Steven Fackler 提交于
-
由 Ralf Jung 提交于
-
由 Guillaume Gomez 提交于
-
由 bors 提交于
Remove some `Vec` allocations to improve performance This claws back most of the performance lost in https://github.com/rust-lang/rust/pull/69745. r? @EddyB
-
由 bors 提交于
Don't run various MIR optimizations at mir-opt-level=0 Add missing checks for mir-opt-level to non-essential MIR passes. I verified that this can still bootstrap even with these passes disabled. r? @oli-obk cc @RalfJung
-
由 bors 提交于
Rollup of 6 pull requests Successful merges: - #68716 (Stabilize `Span::mixed_site`) - #71263 (Remove unused abs_path method from rustc_span::source_map::FileLoader) - #71409 (Point at the return type on `.into()` failure caused by `?`) - #71419 (add message for resolution failure because wrong namespace) - #71438 (Tweak some suggestions in `rustc_resolve`) - #71589 (remove Unique::from for shared pointer types) Failed merges: r? @ghost
-
由 Dylan DPC 提交于
remove Unique::from for shared pointer types r? @SimonSapin
-
由 Dylan DPC 提交于
Tweak some suggestions in `rustc_resolve`
-
由 Dylan DPC 提交于
add message for resolution failure because wrong namespace closes https://github.com/rust-lang/rust/issues/71406
-
由 Dylan DPC 提交于
Point at the return type on `.into()` failure caused by `?` Fix #35946.
-
由 Dylan DPC 提交于
Remove unused abs_path method from rustc_span::source_map::FileLoader
-
由 Dylan DPC 提交于
Stabilize `Span::mixed_site` Closes https://github.com/rust-lang/rust/issues/65049. cc https://github.com/rust-lang/rust/issues/54727#issuecomment-580647446 Pre-requisite for https://github.com/rust-lang/rust/pull/68717 ("Stabilize fn-like proc macros in expression, pattern and statement positions"). Stabilization report: https://github.com/rust-lang/rust/pull/68716#issuecomment-581076337.
-
由 Steven Fackler 提交于
-
由 bors 提交于
submodules: update clippy from 891e1a85 to d01a4981 Changes: ```` `predecessors_for` will be removed soon Rustup "Remove `BodyAndCache`" span_lint_and_note now takes an Option<Span> for the note_span instead of just a span Make lint also capture blocks and closures, adjust language to mention other mutex types don't test the code in the lint docs Switch to matching against full paths instead of just the last element of the path Lint for holding locks across await points fix crash on issue-69020-assoc-const-arith-overflow.rs update stderr file util/fetch_prs_between.sh: Add Markdown formatted Link factor ifs into function, add differing mutex test Update the changelog update documentation Apply suggestions from PR review update span_lint_and_help call to six args test for mutex eq, add another test case use if chain cargo dev fmt fix map import to rustc_middle dev update_lints fix internal clippy warnings change visitor name to OppVisitor use Visitor api to find Mutex::lock calls add note about update-all-refs script, revert redundant pat to master move closures to seperate fns, remove known problems use span_lint_and_help, cargo dev fmt creating suggestion progress work on suggestion for auto fix Implement unsafe_derive_deserialize lint Update empty_enum.stderr Formatting and naming Formatting and naming Cleanup: `node_id` -> `hir_id` Fix issue #2907. Don't trigger toplevel_ref_arg for `for` loops Cleanup: future_not_send: use `return_ty` method Remove badge FIXME from Cargo.toml Change note_span argument for span_lint_and_note. Add an Option<Span> argument to span_lint_and_help. Fixes internal lint warning in code base. Implement collapsible_span_lint_calls lint. ```` Fixes #71453 r? @Dylan-DPC
-
由 Vadim Petrochenkov 提交于
-
由 Vadim Petrochenkov 提交于
Introduce `enum TlsModel` instead.
-
由 LeSeulArtichaut 提交于
-
由 bors 提交于
Rollup of 5 pull requests Successful merges: - #71421 (Add a function to turn Box<T> into Box<[T]>) - #71537 (Remove support for self-opening) - #71551 (Minor refactoring around IndexVec usage in generator transformation) - #71569 ([miri] Throw UB if target size and data size don't match) - #71576 (check that `AsRef` and `AsMut` are inlined) Failed merges: - #71558 (Cleanup and document `-Z tls-model` ) r? @ghost
-
由 Dylan DPC 提交于
check that `AsRef` and `AsMut` are inlined Adds a regression test for #58867 r? @Dylan-DPC
-
由 Dylan DPC 提交于
[miri] Throw UB if target size and data size don't match Issue: https://github.com/rust-lang/miri/issues/1355 If an extern C function is defined as ``` extern "C" { fn malloc(size: u32) -> *mut std::ffi::c_void; } ``` on a 64-bit machine(ie. pointer sizes don't match), return undefined behaviour from Miri when [converting the argument into machine_usize](https://github.com/rust-lang/miri/blob/master/src/shims/foreign_items.rs#L200)
-
由 Dylan DPC 提交于
Remove support for self-opening This was only used for linkage test cases, which is already covered by the [run-make-fulldeps/symbol-visibility test](https://github.com/rust-lang/rust/blob/master/src/test/run-make-fulldeps/symbol-visibility/Makefile) -- which fairly extensively makes sure we're correctly exporting the right symbols at the right visibility (for various Rust crate types). This fixes #10379 and resolves #10356 by removing the test case (and underlying support in the compiler). AFAICT, the better way to test visibility is via nm, like the symbol visibility test. It seems like that's sufficient; I suspect that given that we don't use this we should just drop it (android is tier 2 anyway). But happy to hear otherwise.
-
由 Dylan DPC 提交于
Add a function to turn Box<T> into Box<[T]> Hi, I think this is very useful, as currently it's not possible in safe rust to do this without re-allocating. an alternative implementation of the same function can be: ```rust pub fn into_boxed_slice<T>(boxed: Box<T>) -> Box<[T]> { unsafe { let slice = slice::from_raw_parts_mut(Box::into_raw(boxed), 1); Box::from_raw(slice) } } ``` The only thing that makes me a little uncomfortable is this line : > The alignment of array types is greater or equal to the alignment of its element type from https://rust-lang.github.io/unsafe-code-guidelines/layout/arrays-and-slices.html But then I see: > The alignment of &T, &mut T, *const T and *mut T are the same, and are at least the word size. > The alignment of &[T] is the word size. from https://rust-lang.github.io/unsafe-code-guidelines/layout/pointers.html#representation So I do believe this is valid(FWIW it also passes in miri https://play.rust-lang.org/?gist=c002b99364ee6b29862aeb3565a91c19)
-
由 Esteban Küber 提交于
Fix #35946.
-
由 Esteban Küber 提交于
-
由 Ralf Jung 提交于
-
由 Ralf Jung 提交于
-
- 26 4月, 2020 3 次提交
-
-
由 bors 提交于
Rollup of 5 pull requests Successful merges: - #71490 (Cleanup and document `-C relocation-model`) - #71562 (fix more clippy warnings) - #71571 (Fix since attribute for nonzero_bitor impl's) - #71574 (proc_macro: Fix since attributes for new Span methods) - #71575 (Fix stable(since) attribute for BTreeMap::remove_entry) Failed merges: r? @ghost
-
由 Vadim Petrochenkov 提交于
-
由 Samrat Man Singh 提交于
-