rust/src/librustc_mir/transform/const_prop.rs, branch master

mv compiler to compiler/

2020-08-30T15:45:07+00:00

Apply suggestions from code review

2020-08-20T14:56:19+00:00

Co-authored-by: Wesley Wiser

Explain why we are creating an aggregate constant

2020-08-18T11:57:32+00:00

Address review comments

2020-08-18T11:46:11+00:00

Validate the MIR of all optimizations in the mir-opt directory

2020-08-18T11:01:00+00:00

rust_ast::ast => rustc_ast

2020-08-17T20:32:32+00:00

Rollup merge of #75448 - lcnr:rn-as_local_hir_id, r=davidtwco

2020-08-15T03:07:11+00:00

merge `as_local_hir_id` with `local_def_id_to_hir_id` `as_local_hir_id` was defined as just calling `local_def_id_to_hir_id` and I think that having two different ways to call the same method is somewhat confusing. Don't really care about which of these 2 methods we want to keep. Does this require an MCP, considering that these methods are fairly frequently used?

merge `as_local_hir_id` with `local_def_id_to_hir_id`

2020-08-13T14:55:16+00:00

fix span of stack size error

2020-08-12T09:14:49+00:00

Auto merge of #73656 - oli-obk:deaggregate-is-cleanup, r=wesleywiser

2020-08-11T15:38:14+00:00

move Deaggregate pass to post_borrowck_cleanup Reopen of #71946 Only the second commit is from this PR, the other commit is a bugfix that's in the process of getting merged. I'll rebase once that's done In #70073 MIR pass handling got reorganized, but with the goal of not changing behavior (except for disabling some optimizations on opt-level = 0). But there we realized that the Deaggregator pass, while conceptually more of a "cleanup" pass (and one that should be run before optimizations), was run in the middle of the optimization chain. Likely this is an accident of history, so I suggest we try and clean that up by making it a proper cleanup pass. This does change mir-opt output, because deaggregation now runs before const-prop instead of after. r? @wesleywiser @rust-lang/wg-mir-opt cc @RalfJung