about summary refs log tree commit diff
path: root/src/test/ui
AgeCommit message (Collapse)AuthorLines
2018-09-14Auto merge of #54088 - matthewjasper:use-reason-in-dlle-errors, r=pnkfelixbors-0/+25
[NLL] Suggest let binding Closes #49821 Also adds an alternative to `explain_why_borrow_contains_point` that allows changing error messages based on the reason that will be given. This will also be useful for #51026, #51169 and maybe further changes to does not live long enough messages.
2018-09-14Auto merge of #54080 - PramodBisht:issue/53692, r=estebankbors-0/+51
Addressed #53692 @sunjay @estebank @csmoe hopefully this answer #53692 Please let me know if you have any suggestion
2018-09-14Auto merge of #54032 - oli-obk:layout_scalar_ranges, r=eddybbors-0/+5
Add forever unstable attribute to allow specifying arbitrary scalar ranges r? @eddyb for the first commit and @nikomatsakis for the second one
2018-09-14Rollup merge of #54173 - phansch:suggest_valid_crate_type, r=estebankkennytm-3/+93
Suggest valid crate type if invalid crate type is found This adds a suggestion to the `invalid_crate_types` lint. The suggestion is based on the Levenshtein distance to existing crate types. If no suggestion is found it will show the lint without any suggestions. Closes #53958
2018-09-14Auto merge of #53751 - F001:tuple-struct-self-ctor, r=petrochenkov,varkorbors-34/+216
Implement RFC 2302: tuple_struct_self_ctor Tracking issue: https://github.com/rust-lang/rust/issues/51994
2018-09-13Suggest valid crate type if invalidPhilipp Hansch-3/+93
This adds a suggestion to the `invalid_crate_types` lint. The suggestion is based on the Levenshtein distance to existing crate types. If no suggestion is found it will show the lint without any suggestions.
2018-09-14Rollup merge of #53829 - alexcrichton:release-debuginfo, r=michaelwoeristerkennytm-3/+8
Add rustc SHA to released DWARF debuginfo This commit updates the debuginfo that is encoded in all of our released artifacts by default. Currently it has paths like `/checkout/src/...` but these are a little inconsistent and have changed over time. This commit instead attempts to actually define the file paths in our debuginfo to be consistent between releases. All debuginfo paths are now intended to be `/rustc/$sha` where `$sha` is the git sha of the released compiler. Sub-paths are all paths into the git repo at that `$sha`.
2018-09-14Rollup merge of #54147 - agnxy:const-eval-test, r=oli-obkkennytm-0/+55
Add a test that tries to modify static memory at compile-time Attempt to fix #53818 cc @oli-obk
2018-09-13introduce SelfCtorF001-45/+213
2018-09-13implement feature tuple_struct_self_ctorF001-28/+42
2018-09-13Rollup merge of #53371 - estebank:tuple, r=nikomatsakiskennytm-0/+40
Do not emit E0277 on incorrect tuple destructured binding Fix #50333.
2018-09-12Auto merge of #53793 - toidiu:ak-stabalize, r=nikomatsakisbors-578/+733
stabilize outlives requirements https://github.com/rust-lang/rust/issues/44493 r? @nikomatsakis
2018-09-12Add a test that tries to modify static memory at compile-timeAndrew Xu-0/+55
2018-09-12Rollup merge of #54142 - pnkfelix:fix-regression-test-for-16278, r=wesleywiserkennytm-2/+4
Recover proper regression test for issue #16278. Spawned from my note https://github.com/rust-lang/rust/pull/19955#issuecomment-420430761
2018-09-12Rollup merge of #54072 - blitzerr:master, r=Mark-Simulacrumkennytm-155/+0
Stabilization change for mod.rs This change is in response to https://github.com/rust-lang/rust/issues/53125. The patch makes the feature accepted and removes the tests that tested the non-accepted status of the feature.
2018-09-11Do not emit E0277 on incorrect tuple destructured bindingEsteban Küber-0/+40
2018-09-11Recover proper regression test for issue #16278.Felix S. Klock II-2/+4
2018-09-11Auto merge of #53873 - ↵bors-51/+362
nikomatsakis:nll-universe-subtyping-and-pattern-ascription, r=pnkfelix support ascription for patterns in NLL This implements the strategy outlined in [this comment](https://github.com/rust-lang/rust/issues/47184#issuecomment-416669986): - We first extend the NLL subtyping code so it can handle inference variables and subtyping. - Then we extend HAIR patterns with type ascription. - Then we treat the type `T` in `let pat: T = ...` as an ascription. Before landing, a few things: - [x] Fix the WF rule bug (filed a FIXME https://github.com/rust-lang/rust/issues/54105) - [x] Fix an ICE I encountered locally around bound regions, or else file a follow-up - [x] More tests probably =) r? @pnkfelix
2018-09-11Auto merge of #54111 - nikomatsakis:issue-53686-keywords-and-macros, ↵bors-13/+73
r=alexcrichton warn about keywords in macro invocations Fixes #53686 r? @alexcrichton
2018-09-11stabalize infer outlives requirements (RFC 2093).toidiu-578/+733
Co-authored-by: nikomatsakis
2018-09-11we now successfully warn about `async` in macro invocationsNiko Matsakis-13/+26
2018-09-11Use assertion-like static assertionsOliver Schneider-1/+1
2018-09-11Fix const eval of ZST index operations to make the static assertion workOliver Schneider-0/+5
2018-09-11Auto merge of #51363 - japaric:stable-used, r=cramertjbors-39/+6
stabilize #[used] closes #40289 RFC for stabilization: rust-lang/rfcs#2386 r? @Centril Where should this be documented? Currently the documentation is in the unstable book
2018-09-10add test caseNiko Matsakis-0/+47
2018-09-10add FIXME related to `ref x` bindingsNiko Matsakis-13/+2
2018-09-10Auto merge of #54093 - petrochenkov:noinner, r=alexcrichtonbors-3/+16
Feature gate non-builtin attributes in inner attribute position Closes item 3 from https://github.com/rust-lang/rust/pull/50911#issuecomment-411605393
2018-09-10Add rustc SHA to released DWARF debuginfoAlex Crichton-3/+8
This commit updates the debuginfo that is encoded in all of our released artifacts by default. Currently it has paths like `/checkout/src/...` but these are a little inconsistent and have changed over time. This commit instead attempts to actually define the file paths in our debuginfo to be consistent between releases. All debuginfo paths are now intended to be `/rustc/$sha` where `$sha` is the git sha of the released compiler. Sub-paths are all paths into the git repo at that `$sha`.
2018-09-10propagate user-ascribes types down onto resulting bindingsNiko Matsakis-18/+79
But only in very simple cases.
2018-09-10expand the patterns test with a bunch more scenariosNiko Matsakis-5/+172
2018-09-10optimize `let x: T = ..` to avoid a temporaryNiko Matsakis-34/+31
For some weird reason this fixes `intrinsic-move-val`. It also affects various test heuristics. I removed one test (`reborrow_basic`) that didn't seem to really be testing anything in particular anymore, compared to all the other tests we've got.
2018-09-10WIP remove incorrect nll.stderr reference filesNiko Matsakis-56/+0
2018-09-10fix SCCs containing mixture of universesNiko Matsakis-0/+31
And add a test showing a universe violation getting caught.
2018-09-10insert `AscribeUserType` for ascriptionsNiko Matsakis-19/+100
2018-09-10now that we can handle subtyping, fix higher-ranked equalityNiko Matsakis-12/+1
2018-09-10add a test for variables used twiceNiko Matsakis-0/+52
2018-09-10Auto merge of #54011 - eddyb:anchored-in-the-future, r=petrochenkovbors-0/+278
rustc_resolve: inject `uniform_paths` canaries regardless of the feature-gate, on Rust 2018. This PR is an attempt at future-proofing "anchored paths" by emitting the same ambiguity errors that `#![feature(uniform_paths)]` would, with slightly changed phrasing (see added UI tests). Also, on top of #54005, this PR allows this as well: ```rust use crate_name; use crate_name::foo; ``` In that any ambiguity between an extern crate and an import *of that same crate* is ignored. r? @petrochenkov cc @aturon @Centril @joshtriplett
2018-09-10rustc_resolve: ignore uniform_paths canaries that resolve to an import of ↵Eduard-Mihai Burtescu-0/+62
the same crate.
2018-09-10rustc_resolve: inject `uniform_paths` canaries regardless of the ↵Eduard-Mihai Burtescu-0/+216
feature-gate, on Rust 2018.
2018-09-10Auto merge of #53565 - PramodBisht:issue/53359_b, r=estebankbors-8/+42
#53359: putting multiple unresolved import on single line r? @estebank Here is WIP implementation of #53359 this PR have clubbed multiple unresolved imports into a single line. I think still two things need to improve like giving specific `label message` for each span of multi_span(how we can do this?) and second we are getting a warning while compiling, stating something like `E0432` have been passed before.
2018-09-10Auto merge of #53854 - davidtwco:issue-53668, r=nikomatsakisbors-0/+210
if- and while-let-chains, take 2 - edition changes Part of #53668. r? @nikomatsakis
2018-09-10resolve: Remove `unshadowable_attrs`Vadim Petrochenkov-4/+8
2018-09-10Feature gate non-builtin attributes in inner attribute positionVadim Petrochenkov-3/+16
2018-09-09Auto merge of #53778 - petrochenkov:shadrelax2, r=nikomatsakisbors-42/+975
resolve: Relax shadowing restrictions on macro-expanded macros Previously any macro-expanded macros weren't allowed to shadow macros from outer scopes. Now only "more macro-expanded" macros cannot shadow "less macro-expanded" macros. See comments to `fn may_appear_after` and added tests for more details and examples. The functional changes are a21f6f588fc28c97533130ae44a6957b579ab58c and 46dd365ce9ca0a6b8653849b80267763c542842a, other commits are refactorings.
2018-09-09update ui testsJorge Aparicio-36/+6
2018-09-09Suggest a let binding to extend temporary lifetimes with NLLMatthew Jasper-0/+25
2018-09-09Auto merge of #54057 - matthiaskrgr:stabilize-edition-plus-clippy, ↵bors-7/+7
r=Mark-Simulacrum Stabilize edition 2018; also updates Clippy, RLS and Cargo Supersedes https://github.com/rust-lang/rust/pull/53999 , https://github.com/rust-lang/rust/pull/53935 Clippy build was failing there because crate_visibility_modifier feature was taken out of edition 2018 and clippy used it. The clippy update enables the corresponding feature explicitly. r? @Mark-Simulacrum
2018-09-0953692: Addressed Estebank's NitsPramod Bisht-1/+8
2018-09-09stabilize `#[used]`Jorge Aparicio-3/+0
closes #40289
2018-09-09Addressed #53692Pramod Bisht-0/+44