about summary refs log tree commit diff
AgeCommit message (Collapse)AuthorLines
2020-03-04PlaceRef<'a, 'tcx> -> PlaceRef<'tcx>Santiago Pastorino-50/+46
2020-03-04Make PlaceRef lifetimes of in_projection be both 'tcxSantiago Pastorino-4/+4
2020-03-04Make PlaceRef lifetimes of is_prefix_of be both 'tcxSantiago Pastorino-4/+4
2020-03-04Make PlaceRef lifetimes of classify_drop_access_kind be both 'tcxSantiago Pastorino-1/+1
2020-03-04Make PlaceRef lifetimes of closure_span be both 'tcxSantiago Pastorino-1/+1
2020-03-04Make PlaceRef lifetimes of move_spans be both 'tcxSantiago Pastorino-1/+1
2020-03-04Make PlaceRef lifetimes of borrowed_content_source be both 'tcxSantiago Pastorino-2/+2
2020-03-04Make PlaceRef lifetimes of describe_field be both 'tcxSantiago Pastorino-1/+1
2020-03-04Make PlaceRef lifetimes of add_moved_or_invoked_closure_note be both 'tcxSantiago Pastorino-1/+1
2020-03-04Make PlaceRef lifetimes of is_upvar_field_projection be both 'tcxSantiago Pastorino-6/+6
2020-03-04Make PlaceRef lifetimes of move_path_for_place be both 'tcxSantiago Pastorino-1/+1
2020-03-04Make PlaceRef lifetimes of move_path_closest_to be both 'tcxSantiago Pastorino-2/+2
2020-03-04Make PlaceRef lifetimes of uninitialized_error_reported be both 'tcxSantiago Pastorino-1/+1
2020-03-04Make PlaceRef lifetimes of move_error_reported be both 'tcxSantiago Pastorino-9/+10
2020-03-04Make PlaceRef lifetimes of borrow_conflict_place be both 'tcxSantiago Pastorino-4/+5
2020-03-03Make PlaceRef lifetimes of RootPlace be both 'tcxSantiago Pastorino-6/+6
2020-03-03Make PlaceRef lifetimes of monomorphized_place_ty be both 'tcxSantiago Pastorino-1/+1
2020-03-03Make PlaceRef lifetimes of codegen_place be both 'tcxSantiago Pastorino-3/+3
2020-03-02Make PlaceRef lifetimes of LocalAnalyzer::process_place be both 'tcxSantiago Pastorino-1/+1
2020-03-02Make PlaceRef lifetimes of Place::as_ref be both 'tcxSantiago Pastorino-1/+1
2020-03-02Auto merge of #69635 - Dylan-DPC:rollup-2oh8uu5, r=Dylan-DPCbors-95/+688
Rollup of 6 pull requests Successful merges: - #68682 (Add documentation to compiler intrinsics) - #69544 (Unrevert "Remove `checked_add` in `Layout::repeat`") - #69617 (constify mem::forget) - #69622 (Rename `syntax` in librustc_ast/README.md) - #69623 (stash API: remove panic to fix ICE.) - #69624 (Toolstate: Don't block beta week on already broken tools.) Failed merges: - #69626 (Toolstate: don't duplicate nightly tool list.) r? @ghost
2020-03-02Rollup merge of #69624 - ehuss:toolstate-beta-regress, r=Mark-SimulacrumDylan DPC-63/+133
Toolstate: Don't block beta week on already broken tools. This changes it so that tools are allowed to be broken entering the beta week if they are already broken. This restores the original behavior before the changes in #69332. Closes #68458
2020-03-02Rollup merge of #69623 - Centril:fix-69396-tmp, r=petrochenkovDylan DPC-14/+74
stash API: remove panic to fix ICE. Implements the temporary solution suggested in https://github.com/rust-lang/rust/pull/69537#issuecomment-593143975. Fixes https://github.com/rust-lang/rust/issues/69396. r? @petrochenkov
2020-03-02Rollup merge of #69622 - LeSeulArtichaut:patch-2, r=CentrilDylan DPC-1/+1
Rename `syntax` in librustc_ast/README.md Related to e94d3b7. r? @petrochenkov
2020-03-02Rollup merge of #69617 - DutchGhost:master, r=LukasKalbertodtDylan DPC-1/+2
constify mem::forget implements https://github.com/rust-lang/rust/issues/69616
2020-03-02Rollup merge of #69544 - lqd:unrevert-67174, r=Mark-SimulacrumDylan DPC-7/+5
Unrevert "Remove `checked_add` in `Layout::repeat`" This reapplies @kraai's original `libcore::alloc::Layout::repeat` change from #67174 which was temporarily reverted in #69241. Now that the proper LLVM fix has been cherry-picked, we can unrevert the revert. This change was originally reviewed by @hanna-kruppe on the initial PR. cc @RalfJung
2020-03-02Rollup merge of #68682 - LeSeulArtichaut:stable-intrinsics, r=steveklabnikDylan DPC-9/+473
Add documentation to compiler intrinsics This adds documentation to the compiler intrinsics having stable standard implementations. Relates to #34338 (cc @bstrie) r? @steveklabnik (for reassignment?)
2020-03-02actually mark the function constDutchGhost-1/+1
2020-03-02Auto merge of #69257 - RalfJung:layout-visitor, r=eddybbors-203/+238
Adjust Miri value visitor, and doc-comment layout components I realized that I still didn't have quite the right intuition for how our `LayoutDetails` work, so I had to adjust the Miri value visitor to the things I understood better now. I also added some doc-comments to `LayoutDetails` as a hopefully canonical place to note such things. The main visitor change is that we *first* look at all the fields (according to `FieldPlacement`), and *then* check the variants and handle `Multiple` appropriately. I did not quite realize how orthogonal "fields" and "variants" are. I also moved the check for the scalar ABI to *after* checking all the fields; this leads to better (more type-driven) error messages. And it looks like we can finally remove that magic hack for `ty::Generator`. :D r? @oli-obk for the Miri/visitor changes and @eddyb for the layout docs The Miri PR is at: https://github.com/rust-lang/miri/pull/1178
2020-03-02Auto merge of #69469 - matthewjasper:type-flags, r=cramertjbors-148/+136
Clean up TypeFlags * Add a new method `has_infer_types_or_consts` that's used instead of `has_infer_types` most of the time, since there's generally no reason to only consider types. * Remove `has_closure_types`/`HAS_TY_CLOSURE`, because closures are no longer implicitly linked to the `InferCtxt`. * Reorder flags to group similar ones together * Make some flags more granular * Compute `HAS_FREE_LOCAL_NAMES` from the other flags * Add some more doc comments
2020-03-02Auto merge of #69442 - jakevossen5:master, r=Mark-Simulacrumbors-17/+42
`--explain` disambiguates no long description and invalid error codes Closes #44710 First code contribution here, so feedback is very much appreciated! cc @zackmdavis cc @Mark-Simulacrum
2020-03-02Auto merge of #69432 - petrochenkov:alldeps, r=eddybbors-24/+5
rustc_metadata: Load metadata for indirect macro-only dependencies Imagine this dependency chain between crates ``` Executable crate -> Library crate -> Macro crate ``` where "Library crate" uses the macros from "Macro crate" for some code generation, but doesn't reexport them any further. Currently, when compiling "Executable crate" we don't even load metadata for it, because why would we want to load any metadata from "Macro crate" if it already did all its code generation job when compiling "Library crate". Right? Wrong! Hygiene data and spans (https://github.com/rust-lang/rust/issues/68686, https://github.com/rust-lang/rust/pull/68941) from "Macro crate" still may need to be decoded from "Executable crate". So we'll have to load them properly. Questions: - How this will affect compile times for larger crate trees in practice? How to measure it? Hygiene/span encoding/decoding will necessarily slow down compilation because right now we just don't do some work that we should do, but this introduces a whole new way to slow down things. E.g. loading metadata for `syn` (and its dependencies) when compiling your executable if one of its library dependencies uses it. - We are currently detecting whether a crate reexports macros from "Macro crate" or not, could we similarly detect whether a crate "reexports spans" and keep it unloaded if it doesn't? Or at least "reexports important spans" affecting hygiene, we can probably lose spans that only affect diagnostics.
2020-03-01Toolstate: Don't block beta week on already broken tools.Eric Huss-63/+133
2020-03-02stash API: remove panic to fix ICE.Mazdak Farrokhzad-14/+74
2020-03-01Rename `syntax` in librustc_ast/README.mdLeSeulArtichaut-1/+1
2020-03-01Clean up TypeFlagsMatthew Jasper-87/+99
* Reorder flags to group similar ones together * Make some flags more granular * Compute `HAS_FREE_LOCAL_NAMES` from the other flags * Remove `HAS_TY_CLOSURE` * Add some more doc comments
2020-03-01Fix use of `has_infer_types`Matthew Jasper-61/+37
* Add a new method `has_infer_types_or_consts` that's used instead most of the time, since there's generally no reason to only consider types. * Remove use of `has_closure_types`, because closures are no longer implicitly linked to the `InferCtxt`.
2020-03-01Auto merge of #69408 - RalfJung:canonical-alloc-id, r=oli-obkbors-66/+58
Miri: let machine canonicalize AllocIDs This implements the rustc side of the plan I laid out [here](https://github.com/rust-lang/miri/pull/1147#issuecomment-581868901). Miri PR: https://github.com/rust-lang/miri/pull/1190
2020-03-01constify mem::forgetDutchGhost-0/+1
2020-03-01Auto merge of #69612 - Dylan-DPC:rollup-f180gcc, r=Dylan-DPCbors-42/+55
Rollup of 7 pull requests Successful merges: - #69504 (Use assert_ne in hash tests) - #69554 (Cleanup e0374) - #69568 (Clarify explanation of Vec<T> 'fn resize') - #69569 (simplify boolean expressions) - #69577 (Clean up E0375 explanation) - #69598 (rustdoc: HTML escape crate version) - #69607 (Clean up E0376 explanation) Failed merges: r? @ghost
2020-03-01Rollup merge of #69607 - GuillaumeGomez:cleanup-e0376, r=Dylan-DPCDylan DPC-10/+11
Clean up E0376 explanation r? @Dylan-DPC
2020-03-01Rollup merge of #69598 - ollie27:rustdoc_crate-version_escape, r=GuillaumeGomezDylan DPC-2/+9
rustdoc: HTML escape crate version As `--crate-version` accepts arbitrary strings they need to be escaped. r? @GuillaumeGomez
2020-03-01Rollup merge of #69577 - GuillaumeGomez:cleanup-e0375, r=Dylan-DPCDylan DPC-8/+11
Clean up E0375 explanation r? @Dylan-DPC
2020-03-01Rollup merge of #69569 - matthiaskrgr:nonminimal_bool, r=mark-SimulacrumDylan DPC-13/+13
simplify boolean expressions
2020-03-01Rollup merge of #69568 - JOE1994:patch-2, r=Dylan-DPCDylan DPC-2/+3
Clarify explanation of Vec<T> 'fn resize' 1. Clarified on what should implement `Clone` trait. 2. Minor grammar fix: to be able clone => to be able **to** clone
2020-03-01Rollup merge of #69554 - GuillaumeGomez:cleanup-e0374, r=Dylan-DPCDylan DPC-6/+8
Cleanup e0374 r? @Dylan-DPC
2020-03-01Rollup merge of #69504 - MichaelMcDonnell:hash_assert_ne, r=LukasKalbertodtDylan DPC-1/+0
Use assert_ne in hash tests The hash tests were written before the assert_ne macro was added to the standard library. The assert_ne macro provides better output in case of a failure.
2020-03-01Remove assert that had been replaced by assert_neMichael Mc Donnell-1/+0
2020-03-01Auto merge of #69380 - Zoxc:parent-module, r=michaelwoeristerbors-21/+25
Use a query to get parent modules Split out from https://github.com/rust-lang/rust/pull/69015 / https://github.com/rust-lang/rust/pull/68944. r? @michaelwoerister
2020-03-01Clean up E0376 explanationGuillaume Gomez-10/+11