about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorLines
2020-01-29Add an option to use LLD to link the compiler on Windows platformsJohn Kåre Alsaker-7/+56
2020-01-29Auto merge of #68635 - JohnTitor:rollup-jsc34ac, r=JohnTitorbors-41/+98
Rollup of 7 pull requests Successful merges: - #67722 (Minor: note how Any is an unsafe trait in SAFETY comments) - #68586 (Make conflicting_repr_hints a deny-by-default c-future-compat lint) - #68598 (Fix null synthetic_implementors error) - #68603 (Changelog: Demonstrate final build-override syntax) - #68609 (Set lld flavor for MSVC to link.exe) - #68611 (Correct ICE caused by macros generating invalid spans.) - #68627 (Document that write_all will not call write if given an empty buffer) Failed merges: r? @ghost
2020-01-29Rollup merge of #68627 - joshtriplett:write-all-none, r=Dylan-DPCYuki Okushi-0/+2
Document that write_all will not call write if given an empty buffer Some types of Write instances have a semantic meaning associated with writing an empty buffer, such as sending an empty packet. This works when calling `write` directly, and supplying an empty buffer. However, calling `write_all` on an empty buffer will simply never call `write`, because `write_all` assumes it has no work to do. Document this behavior, to help prospective users of datagram-packet-style Write instances.
2020-01-29Rollup merge of #68611 - MichaelBurge:master, r=estebankYuki Okushi-1/+8
Correct ICE caused by macros generating invalid spans. Closes #68605
2020-01-29Rollup merge of #68609 - Zoxc:lld-msvc, r=alexcrichtonYuki Okushi-2/+5
Set lld flavor for MSVC to link.exe This enables linking with LLD on Windows with just `-C linker=rust-lld` instead of needing `-C linker=rust-lld -C linker-flavor=lld-link`.
2020-01-29Rollup merge of #68603 - kornelski:patch-1, r=pietroalbiniYuki Okushi-2/+2
Changelog: Demonstrate final build-override syntax
2020-01-29Rollup merge of #68598 - GuillaumeGomez:fix-null-synthetic_implementors, ↵Yuki Okushi-14/+16
r=ollie27 Fix null synthetic_implementors error Fixes #68584. r? @ollie27 cc @kinnison
2020-01-29Rollup merge of #68586 - Centril:repr-deny, r=pnkfelixYuki Okushi-20/+59
Make conflicting_repr_hints a deny-by-default c-future-compat lint Closes https://github.com/rust-lang/rust/issues/68428. cc https://github.com/rust-lang/rust/issues/68585. r? @petrochenkov @pnkfelix
2020-01-29Rollup merge of #67722 - petertodd:2019-improve-any-comment, r=Mark-SimulacrumYuki Okushi-2/+6
Minor: note how Any is an unsafe trait in SAFETY comments Motivation: helpful to people like myself reading the standard library source to better understand how to use Any, especially if we do go ahead with https://github.com/rust-lang/rust/pull/67562 and make it an unsafe trait.
2020-01-29Auto merge of #68572 - tmiasko:sanitizer-use-after-scope, r=nikicbors-5/+105
Detect use-after-scope bugs with AddressSanitizer Enable use-after-scope checks by default when using AddressSanitizer. They allow to detect incorrect use of stack objects after their scope have already ended. The detection is based on LLVM lifetime intrinsics. To facilitate the use of this functionality, the lifetime intrinsics are now emitted regardless of optimization level if enabled sanitizer makes use of them.
2020-01-29Auto merge of #68512 - spastorino:local-is-copy, r=oli-obkbors-130/+134
Local is copy r? @oli-obk
2020-01-28Minor: note why we can rely on Any trait for safetyPeter Todd-2/+6
2020-01-29Auto merge of #68625 - JohnTitor:rollup-20pfcru, r=JohnTitorbors-41/+203
Rollup of 8 pull requests Successful merges: - #68289 (Don't ICE on path-collision in dep-graph) - #68378 (Add BTreeMap::remove_entry) - #68553 (Fix run button positionning in case of scrolling) - #68556 (rustdoc: Fix re-exporting primitive types) - #68582 (Add E0727 long explanation) - #68592 (fix: typo in vec.rs) - #68619 (Fix a few spelling mistakes) - #68620 (Update links to WASI docs in time.rs module) Failed merges: r? @ghost
2020-01-28Document that write_all will not call write if given an empty bufferJosh Triplett-0/+2
Some types of Write instances have a semantic meaning associated with writing an empty buffer, such as sending an empty packet. This works when calling `write` directly, and supplying an empty buffer. However, calling `write_all` on an empty buffer will simply never call `write`, because `write_all` assumes it has no work to do. Document this behavior, to help prospective users of datagram-packet-style Write instances.
2020-01-29Rollup merge of #68620 - kubkon:patch-1, r=Dylan-DPCYuki Okushi-2/+2
Update links to WASI docs in time.rs module Since the docs for the WASI API are now evolving in [WebAssembly/WASI] repo, I thought it might be useful to update the links in the docs to point to that location instead of using the outdated `CraneStation/wasmtime` destination. [WebAssembly/WASI]: https://github.com/WebAssembly/WASI r? @steveklabnik cc @alexcrichton
2020-01-29Rollup merge of #68619 - gorilskij:master, r=varkorYuki Okushi-2/+2
Fix a few spelling mistakes
2020-01-29Rollup merge of #68592 - pdbrito:master, r=jonas-schievinkYuki Okushi-1/+1
fix: typo in vec.rs
2020-01-29Rollup merge of #68582 - LeSeulArtichaut:code-explanations, r=Dylan-DPCYuki Okushi-1/+27
Add E0727 long explanation Add long explanation for the `E0727` error code (async generators not yet supported). Part of #61137 r? @GuillaumeGomez
2020-01-29Rollup merge of #68556 - ollie27:rustdoc_primitive_re-export, r=GuillaumeGomezYuki Okushi-17/+91
rustdoc: Fix re-exporting primitive types * Generate links to the primitive type docs for re-exports. * Don't ICE on cross crate primitive type re-exports. * Make primitive type re-exports show up cross crate. Fixes #67646 Closes #67972 r? @GuillaumeGomez
2020-01-29Rollup merge of #68553 - GuillaumeGomez:fix-run-button-scroll-pos, r=kinnisonYuki Okushi-8/+7
Fix run button positionning in case of scrolling Fixes #68337. r? @kinnison
2020-01-29Rollup merge of #68378 - billyrieger:btreemap-remove-entry, r=KodrAusYuki Okushi-1/+30
Add BTreeMap::remove_entry Implements https://github.com/rust-lang/rust/issues/66714.
2020-01-29Rollup merge of #68289 - ↵Yuki Okushi-9/+43
pnkfelix:issue-62649-dont-ice-on-path-collision-in-dep-graph, r=michaelwoerister Don't ICE on path-collision in dep-graph Collisions in the dep-graph due to path-reuse are rare but can occur. So, instead of ICE'ing, just fail to mark green in such cases (for `DepKind::{Hir, HirBody, CrateMetadata}`). Fix #62649.
2020-01-28Update links to WASI docs in time.rs moduleJakub Konka-2/+2
Since the docs for the WASI API are now evolving in [WebAssembly/WASI] repo, I thought it might be useful to update the links in the docs to point to that location instead of using the outdated `CraneStation/wasmtime` destination. [WebAssembly/WASI]: https://github.com/WebAssembly/WASI
2020-01-28Fix null synthetic_implementors errorGuillaume Gomez-14/+16
2020-01-28Fix a few spelling mistakesgorilskij-2/+2
2020-01-28Auto merge of #68606 - jonas-schievink:normalize-fastpath, r=Zoxcbors-0/+4
Add an early-exit to `QueryNormalizer::fold_ty` Pulled out from https://github.com/rust-lang/rust/pull/68524, this results in a ~60-70% reduction in compile time for the await-call-tree benchmarks. This should unblock https://github.com/rust-lang/rust/issues/67982 as well. r? @Zoxc
2020-01-28Add E0727 long explanationLeSeulArtichaut-1/+27
2020-01-28Correct ICE caused by macros generating invalid spans.Michael Burge-1/+8
2020-01-28Demonstrate final build-override syntaxKornel-2/+2
2020-01-28Set lld flavor for MSVC to link.exeJohn Kåre Alsaker-2/+5
2020-01-28Add an early-exit to `QueryNormalizer::fold_ty`Jonas Schievink-0/+4
2020-01-28Auto merge of #68533 - tmiasko:compiletest, r=nikomatsakisbors-125/+280
compiletest: Unit tests for `EarlyProps` (+ small cleanup) * Parse `EarlyProps` from a reader * Add unit tests for `EarlyProps` * Remove unused `llvm-cxxflags` option * Remove unnecessary memory allocations in `iter_header` * Update mode list displayed in `--help`
2020-01-28Fix some wrong dereferences after rebaseSantiago Pastorino-3/+3
2020-01-28Remove unneeded & on match patternSantiago Pastorino-2/+2
2020-01-28./x.py fmtSantiago Pastorino-10/+14
2020-01-28Place::ty_from takes local by valueSantiago Pastorino-47/+47
2020-01-28Local field on PlaceRef and RootPlace is not a reference anymoreSantiago Pastorino-90/+90
2020-01-28codegen_place and related functions can take PlaceRef by valueSantiago Pastorino-19/+19
2020-01-28make_integrate_local takes Local by valueSantiago Pastorino-4/+4
2020-01-28record_killed_borrows_for_local takes Local by valueSantiago Pastorino-4/+4
2020-01-28Place conflict functions take Local by valueSantiago Pastorino-6/+6
2020-01-28Auto merge of #68529 - TimDiekmann:rename-alloc, r=Amanieubors-45/+60
Rename `Alloc` to `AllocRef` The allocator-wg has decided to merge this change upstream in https://github.com/rust-lang/wg-allocators/issues/8#issuecomment-577122958. This renames `Alloc` to `AllocRef` because types that implement `Alloc` are a reference, smart pointer, or ZSTs. It is not possible to have an allocator like `MyAlloc([u8; N])`, that owns the memory and also implements `Alloc`, since that would mean, that moving a `Vec<T, MyAlloc>` would need to correct the internal pointer, which is not possible as we don't have move constructors. For further explanation please see https://github.com/rust-lang/wg-allocators/issues/8#issuecomment-489464843 and the comments after that one. Additionally it clarifies the semantics of `Clone` on an allocator. In the case of `AllocRef`, it is clear that the cloned handle still points to the same allocator instance, and that you can free data allocated from one handle with another handle. The initial proposal was to rename `Alloc` to `AllocHandle`, but `Ref` expresses the semantics better than `Handle`. Also, the only appearance of `Handle` in `std` are for windows specific resources, which might be confusing. Blocked on https://github.com/rust-lang/miri/pull/1160
2020-01-28fix: typo in vec.rsPedro de Brito-1/+1
2020-01-28Add BTreeMap::remove_entryBilly Rieger-1/+30
Mainly for API parity with HashMap. - Add BTreeMap::remove_entry - Rewrite BTreeMap::remove to use remove_entry - Use btreemap_remove_entry feature in doc comment
2020-01-28Auto merge of #68234 - CAD97:slice-from-raw-parts, r=KodrAusbors-8/+5
Stabilize ptr::slice_from_raw_parts[_mut] Closes #36925, the tracking issue. Initial impl: #60667 r? @rust-lang/libs In addition to stabilizing, I've adjusted the example of `ptr::slice_from_raw_parts` to use `slice_from_raw_parts` instead of `slice_from_raw_parts_mut`, which was unnecessary for the example as written.
2020-01-28Auto merge of #68587 - JohnTitor:rollup-fz45xwc, r=JohnTitorbors-47/+102
Rollup of 11 pull requests Successful merges: - #68200 (Stabilize the debug_map_key_value feature) - #68383 (Clean up E0205 explanation) - #68412 (Clean up E0207 explanation) - #68454 (clean up E0214 explanation) - #68482 (clean up error codes explanation) - #68563 (Don't call `tcx.fn_sig` on closures) - #68570 (Bump LLVM submodule to fix LLVM assertion failure in MSP430 interrupt generation.) - #68571 (check_match: extract common logic) - #68573 (Clean up E0262 explanation) - #68575 (Disable the testcase for Vxworks.) - #68581 (Add support for icebreakers-cleanup-crew commands) Failed merges: r? @ghost
2020-01-28Rollup merge of #68581 - spastorino:support-ice-breaker-cleanup-crew, ↵Yuki Okushi-0/+11
r=Dylan-DPC Add support for icebreakers-cleanup-crew commands r? @nikomatsakis
2020-01-28Rollup merge of #68575 - Wind-River:master_2020, r=alexcrichtonYuki Okushi-0/+1
Disable the testcase for Vxworks. r? @alexcrichton
2020-01-28Rollup merge of #68573 - GuillaumeGomez:clean-up-e0262, r=Dylan-DPCYuki Okushi-3/+7
Clean up E0262 explanation r? @Dylan-DPC
2020-01-28Rollup merge of #68571 - Centril:check_in_cx, r=oli-obkYuki Okushi-5/+8
check_match: extract common logic This is part of work on `hir::ExprKind::Let` which I thought made sense on its own (though makes even more sense with `::Let`). r? @oli-obk
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-05-06 10:40:52 +0000