about summary refs log tree commit diff
path: root/src
AgeCommit message (Collapse)AuthorLines
2019-08-11Auto merge of #63343 - ishitatsuyuki:revert-62150, r=RalfJungbors-5/+40
Back out #62150 Ref: #62825 cc @RalfJung
2019-08-11Auto merge of #63413 - RalfJung:miri, r=oli-obkbors-9/+8
update Miri With https://github.com/rust-lang/rust/pull/63404 landed, we need https://github.com/rust-lang/miri/pull/898 to avoid failures in https://github.com/RalfJung/miri-test-libstd. r? @oli-obk
2019-08-10Auto merge of #63250 - petrochenkov:descrate, r=davidtwcobors-73/+62
diagnostics: Describe crate root modules in `DefKind::Mod` as "crate" Or we can use "extern crate" like resolve previously did sometimes, not sure. r? @davidtwco
2019-08-10Apply suggestions from code reviewJakub Adam Wieczorek-35/+35
Co-Authored-By: Mazdak Farrokhzad <twingoow@gmail.com>
2019-08-10Suggest using a qualified path in patterns with inconsistent bindingsJakub Adam Wieczorek-49/+159
A program like the following one: ```rust enum E { A, B, C } fn f(x: E) -> bool { match x { A | B => false, C => true } } ``` is rejected by the compiler due to `E` variant paths not being in scope. In this case `A`, `B` are resolved as pattern bindings and consequently the pattern is considered invalid as the inner or-patterns do not bind to the same set of identifiers. This is expected but the compiler errors that follow could be surprising or confusing to some users. This commit adds a help note explaining that if the user desired to match against variants or consts, they should use a qualified path. The note is restricted to cases where the identifier starts with an upper-case sequence so as to reduce the false negatives. Since this happens during resolution, there's no clean way to check what the patterns match against. The syntactic criterium, however, is in line with the convention that's assumed by the `non-camel-case-types` lint.
2019-08-10Update cargoVadim Petrochenkov-0/+0
2019-08-10diagnostics: Describe crate root modules in `DefKind::Mod` as "crate"Vadim Petrochenkov-73/+62
2019-08-10resolve: Remove remaining special cases from built-in macrosVadim Petrochenkov-37/+20
2019-08-10lowering: move lower_arg -> item.rsMazdak Farrokhzad-9/+9
2019-08-10lowering: move scope & capture_clause stuff -> expr.rsMazdak Farrokhzad-66/+66
2019-08-10lowering: refactor into item.rsMazdak Farrokhzad-1417/+1444
2019-08-10lowering: move {lower_arm,arm} -> expr.rsMazdak Farrokhzad-25/+29
2019-08-10lowering: move field -> expr.rsMazdak Farrokhzad-10/+10
2019-08-10lowering: refactor label/dest -> expr.rsMazdak Farrokhzad-47/+43
2019-08-10lowering: move lower_{unop,binop} -> expr.rsMazdak Farrokhzad-34/+34
2019-08-10lowering: move lower_field -> expr.rsMazdak Farrokhzad-10/+10
2019-08-10lowering: move expr builder methods -> expr.rsMazdak Farrokhzad-175/+182
2019-08-10lowering: move make_async_expr -> expr.rsMazdak Farrokhzad-41/+56
2019-08-10lowering: extract lower_expr_letMazdak Farrokhzad-34/+45
2019-08-10lowering: extract lower_expr_ifMazdak Farrokhzad-40/+53
2019-08-10lowering: extract lower_expr_while_in_loop_scopeMazdak Farrokhzad-73/+86
2019-08-10lowering: move wrap_in_try_constructor -> expr.rsMazdak Farrokhzad-12/+11
2019-08-10lowering: extract lower_expr_try_blockMazdak Farrokhzad-25/+18
2019-08-10lowering: move lower_await -> expr.rsMazdak Farrokhzad-163/+160
2019-08-10lowering: extract lower_expr_closureMazdak Farrokhzad-36/+39
2019-08-10lowering: extract lower_expr_async_closureMazdak Farrokhzad-49/+67
2019-08-10lowering: extract lower_expr_range_closedMazdak Farrokhzad-11/+15
2019-08-10lowering: extract lower_expr_rangeMazdak Farrokhzad-39/+44
2019-08-10lowering: extract lower_expr_asmMazdak Farrokhzad-30/+35
2019-08-10lowering: extract lower_expr_yieldMazdak Farrokhzad-22/+24
2019-08-10lowering: extract lower_expr_forMazdak Farrokhzad-153/+163
2019-08-10lowering: extract lower_expr_tryMazdak Farrokhzad-110/+105
2019-08-10lowering: move lower_expr -> expr.rsMazdak Farrokhzad-800/+815
2019-08-10Auto merge of #62955 - Mark-Simulacrum:rustdoc-clean-1, r=eddybbors-186/+97
rustdoc: general cleanups This is purely a refactoring, mostly just simplifying some of the code. Commits are best reviewed individually.
2019-08-10Use Result::unwrap_or_else instead of matchingLzu Tao-4/+1
2019-08-10Add an example to show how to insert item to a sorted vecLzu Tao-0/+14
2019-08-10Derive Debug for CrateInfobjorn3-0/+1
2019-08-10rename RUST_CTFE_BACKTRACE to RUSTC_CTFE_BACKTRACERalf Jung-1/+1
2019-08-10Auto merge of #63437 - Centril:rollup-ryx881p, r=Centrilbors-3942/+4022
Rollup of 4 pull requests Successful merges: - #63400 (Try to break resolve into more isolated parts) - #63425 (Cleanup historical stability comments) - #63429 (.gitignore: Readd `/tmp/`) - #63432 (Cleanup & Simplify stuff in lowering) Failed merges: r? @ghost
2019-08-10Rollup merge of #63432 - Centril:simplify-lowering, r=eddybMazdak Farrokhzad-43/+34
Cleanup & Simplify stuff in lowering Closes https://github.com/rust-lang/rust/issues/60253 as a byproduct. It turns out that it is in fact necessary to have a `DropTemps(...)` around the `match_expr` and there is a test (https://github.com/rust-lang/rust/blob/master/src/test/ui/issues/issue-13304.rs) which fails without that. r? @eddyb
2019-08-10Rollup merge of #63425 - Mark-Simulacrum:clean-stability-doc, r=eddybMazdak Farrokhzad-15/+6
Cleanup historical stability comments These weren't removed by ccbcc720a679ae76155a8 most likely by accident, let's clean them up now.
2019-08-10Revert "Rollup merge of #62150 - alex:mem-uninit-refactor, r=RalfJung"Tatsuyuki Ishi-5/+40
This reverts commit 1d45156866b54c3fc36edfdfcdd8149ad9cb5711, reversing changes made to 0f92eb8a4a7d8715381f5b5d748d22315f6ff9c7.
2019-08-10fix testRalf Jung-6/+55
2019-08-10Implement Clean<Crate> on hir::Crate directlyMark Rousskov-11/+8
2019-08-10Replace is_doc_reachable with is_publicMark Rousskov-20/+7
2019-08-10Remove NodeId from doctree::ModuleMark Rousskov-10/+7
2019-08-10Gather deprecation information during cleaningMark Rousskov-56/+21
2019-08-10Gather stability information during cleaningMark Rousskov-55/+27
2019-08-10Make exact_paths a non-optional field on RustdocVisitorMark Rousskov-12/+11
Also privatizes needlessly public methods to enforce which methods callers are intended to call, i.e., only `new` and `visit`.
2019-08-10Represent ownership transfer in RustdocVisitor::visitMark Rousskov-5/+7
Previously visit could be called multiple times, but this is inaccurate, as it deconstructs Visitor state.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-28 07:56:36 +0000