about summary refs log tree commit diff
path: root/src/test
AgeCommit message (Collapse)AuthorLines
2019-10-06Auto merge of #65043 - Aaron1011:fix/reexport-determinism, r=petrochenkovbors-14/+14
Make re-export collection deterministic Fixes https://github.com/rust-lang/rust/issues/65036 Previously, we were using an `FxHashMap` to collect module re-exports. However, re-exports end up getting serialized into crate metadata, which means that metadata generation was non-deterministic. This resulted in spurious error messages changes (e.g. PR #64906) due to pretty-printing implicitly depending on the order of re-exports when computing the proper path to show to the user. See #65042 for a long-term strategy to detect this kind of issue
2019-10-05Rollup merge of #65151 - tmandry:revert-emscripten-upgrade, r=tmandryTyler Mandry-177/+177
Revert #63649 - "Upgrade Emscripten targets to use upstream LLVM backend" This change caused the runtime of the linux-asmjs builder to nearly double from 2+ hours to about 4 hours, which happens to be the bors timeout. (It made it in barely under 4 hours when it was merged.) This is causing timeouts on all new changes. This reverts commit 7870050796e5904a0fc85ecbe6fa6dde1cfe0c91, reversing changes made to 2e7244807a7878f6eca3eb7d97ae9b413aa49014.
2019-10-05Rollup merge of #65130 - davidtwco:rfc-2008-improper-ctypes, r=petrochenkovTyler Mandry-0/+148
lint: extern non-exhaustive types are improper This PR makes the `improper_ctype` lint trigger for non-exhaustive types when those types aren't defined in the current crate, as per [this comment](https://github.com/rust-lang/rust/issues/44109#issuecomment-537583344). cc @Centril
2019-10-05Rollup merge of #65123 - Centril:mac-invoc-in-mut-pat, r=estebankTyler Mandry-0/+71
Account for macro invocation in `let mut $pat` diagnostic. Fixes https://github.com/rust-lang/rust/issues/65122. r? @estebank
2019-10-05Rollup merge of #65066 - ↵Tyler Mandry-11/+22
wesleywiser:fix_const_prop_ice_on_polymorphic_promoted_mir, r=oli-obk [const-prop] Fix ICE when trying to eval polymorphic promoted MIR Fixes #64908 r? @oli-obk cc @nikomatsakis @pnkfelix
2019-10-05Rollup merge of #65011 - estebank:ice-o-matic, r=zackmdavisTyler Mandry-0/+34
Do not ICE when dereferencing non-Copy raw pointer CC #52262. Confirmed to remove the unnecessary ICE, but without a repro case.
2019-10-05Rollup merge of #64909 - estebank:turbofish-reloaded, r=CentrilTyler Mandry-31/+55
When encountering chained operators use heuristics to recover from bad turbofish
2019-10-05Rollup merge of #64708 - SimonSapin:option-deref, r=CentrilTyler Mandry-6/+2
Stabilize `Option::as_deref` and `Option::as_deref_mut` The tracking issue https://github.com/rust-lang/rust/issues/50264 still has unresolved question for the corresponding `Result` methods.
2019-10-05Revert "Auto merge of #63649 - tlively:emscripten-upstream-upgrade, ↵Tyler Mandry-177/+177
r=alexcrichton" This reverts commit 7870050796e5904a0fc85ecbe6fa6dde1cfe0c91, reversing changes made to 2e7244807a7878f6eca3eb7d97ae9b413aa49014.
2019-10-05Remove `for_each_child_stable`Aaron Hill-14/+14
Now that `Resolutions` has a deterministic iteration order, it's no longer necessary to sort its entries before iterating over them
2019-10-05lint: extern non-exhaustive types are improperDavid Wood-0/+148
This commit makes the `improper_ctype` lint trigger for non-exhaustive types when those types aren't defined in the current crate. Signed-off-by: David Wood <david@davidtw.co>
2019-10-05Account for macro invocation in `let mut $pat` diagnostic.Mazdak Farrokhzad-0/+71
2019-10-04Auto merge of #63649 - tlively:emscripten-upstream-upgrade, r=alexcrichtonbors-177/+177
Upgrade Emscripten targets to use upstream LLVM backend - Refactors the Emscripten target spec to share code with other wasm targets. - Replaces the incorrect wasm32 C call ABI with the old asmjs version, which is correct for both wasm32 and JS. - Updates the varargs ABI used by Emscripten and deletes the old one. - Removes the obsolete wasm32-experimental-emscripten target. - Temporarily makes Emscripten targets use panic=abort by default because supporting unwinding will require an LLVM patch.
2019-10-04Add ignore-asmjs to new testThomas Lively-0/+1
2019-10-04[const-prop] Fix ICE when trying to eval polymorphic promoted MIRWesley Wiser-11/+22
2019-10-04Fix ABI, run and fix more tests, re-enable CI for PRsThomas Lively-101/+113
2019-10-04Upgrade Emscripten targets to use upstream LLVM backendThomas Lively-76/+63
- Refactors the Emscripten target spec to share code with other wasm targets. - Replaces the incorrect wasm32 C call ABI with the old asmjs version, which is correct for both wasm32 and JS. - Updates the varargs ABI used by Emscripten and deletes the old one. - Removes the obsolete wasm32-experimental-emscripten target. - Temporarily makes Emscripten targets use panic=abort by default because supporting unwinding will require an LLVM patch.
2019-10-04Rollup merge of #65073 - ecstatic-morse:issue-65071, r=petrochenkovMazdak Farrokhzad-2/+1
Remove `borrowck_graphviz_postflow` from test Resolves #65071. r? @petrochenkov
2019-10-04Rollup merge of #65026 - petrochenkov:ice1, r=eddybMazdak Farrokhzad-2/+2
metadata: Some crate loading cleanup So, my goal was to fix caching of loaded crates which is broken and causes ICEs like #56935 or #64450. While investigating I found that the code is pretty messy and likes to confuse various things that look similar but are actually different. This PR does some initial cleanup in that area, I hope to get to the caching itself a bit later.
2019-10-04Rollup merge of #64874 - matthewjasper:simplify-euv, r=eddybMazdak Farrokhzad-24/+18
Simplify ExprUseVisitor * Remove HIR const qualification * Remove parts of ExprUseVisitor that aren't being used r? @eddyb
2019-10-04Rollup merge of #64749 - matthewjasper:liveness-opt, r=nikomatsakisMazdak Farrokhzad-478/+24
Fix most remaining Polonius test differences This fixes most of the Polonius test differences and also avoids overflow in issue-38591.rs. r? @nikomatsakis
2019-10-03Rollup merge of #65057 - mathstuf:fix-warning-typo, r=CentrilTyler Mandry-20/+20
typo: fix typo in E0392 See #64931. --- Cc: @Centril @estebank
2019-10-03Rollup merge of #65055 - GuillaumeGomez:long-err-explanation-E0556, ↵Tyler Mandry-1/+2
r=petrochenkov Add long error explanation for E0556 Part of #61137
2019-10-03Rollup merge of #65018 - Aaron1011:fix/backtrace-stderr, r=nikomatsakisTyler Mandry-4/+8
Set RUST_BACKTRACE=0 in tests that include a backtrace in stderr This removes the implicit dependency on the environment variables set when running `./x.py test`
2019-10-03Rollup merge of #64842 - ↵Tyler Mandry-0/+116
pnkfelix:fix-issue-61631-self-in-type-param-default, r=alexreg Disallow Self in type param defaults of ADTs Fix #61631 (also includes a drive-by fix to a typo in some related diagnostic output.)
2019-10-03Rollup merge of #64741 - GuillaumeGomez:prevent-rustdoc-feature-doctests, ↵Tyler Mandry-0/+20
r=QuietMisdreavus Prevent rustdoc feature doctests Part of https://github.com/rust-lang/rust/pull/61351 cc @ollie27
2019-10-03Rollup merge of #64706 - nikomatsakis:issue-60218-test-case, r=centrilTyler Mandry-0/+34
add regression test for #60218 Fixes #60218
2019-10-03Rollup merge of #64690 - petrochenkov:mixed, r=dtolnayTyler Mandry-35/+152
proc_macro API: Expose `macro_rules` hygiene Proc macros do not have direct access to our oldest and most stable hygiene kind - `macro_rules` hygiene. To emulate it macro authors have to go through two steps - first generate a temporary `macro_rules` item (using a derive, at least until https://github.com/rust-lang/rust/pull/64035 is merged), then generate a macro call to that item. Popular crates like [proc_macro_hack](https://crates.io/crates/proc-macro-hack) use this trick to generate hygienic identifiers from proc macros. I'd say that these workarounds with nested macro definitions have more chances to hit some corner cases in our hygiene system, in which we don't have full confidence. So, let's provide a direct access to `macro_rules` hygiene instead. This PR does that by adding a new method `Span::mixed_site` (bikeshedding is welcome) in addition to existing `Span::call_site` (stable) and `Span::def_site` (unstable). Identifiers with this span resolve at def-site in for local variables, labels and `$crate`, and resolve at call-site for everything else, i.e. exactly like identifiers produced by `macro_rules`. This API addition opens the way to stabilizing proc macros in expression positions (https://github.com/rust-lang/rust/issues/54727), for which use of call-site hygiene or workarounds with temporary items would be quite unfortunate. (`macro_rules` expanded in expression position, on the other hand, are stable since 1.0 and widely used.) r? @dtolnay @alexcrichton
2019-10-03Rollup merge of #64675 - Centril:deprecate-plugin, r=oli-obkTyler Mandry-240/+562
Deprecate `#![plugin]` & `#[plugin_registrar]` This PR deprecates `#![plugin]` and `#[plugin_registrar]`. ~A removal deadline is set: 1.44.0. This will be in 9 months from now and should give everyone who is still relying on the feature ample time to rid themselves of this dependency.~ cc https://github.com/rust-lang/rust/issues/29597 r? @Mark-Simulacrum
2019-10-03Bless testDylan MacKenzie-1/+1
2019-10-04metadata: Remove `locator::Context::ident`Vadim Petrochenkov-2/+2
It's a crate name after renaming, so it's entirely irrelevant to crate loading
2019-10-03Remove `borrowck_graphviz_postflow` from testDylan MacKenzie-1/+0
2019-10-03review commentsEsteban Küber-9/+9
2019-10-03review commentsEsteban Küber-12/+27
2019-10-03Prove bad turbofish parser recovery in testEsteban Küber-11/+3
2019-10-03Account for missing turbofish in paths tooEsteban Küber-2/+3
2019-10-03When encountering chained operators use heuristics to recover from bad turbofishEsteban Küber-14/+30
2019-10-03Regression tests.Felix S. Klock II-0/+116
Update: incorporate review feedback.
2019-10-03Auto merge of #64938 - estebank:ice-ice-baby, r=matthewjasperbors-0/+22
Avoid ICE on ReFree region on where clause Fix #64855.
2019-10-03typo: fix typo in E0392Ben Boeckel-20/+20
See #64931.
2019-10-03Auto merge of #64999 - nikomatsakis:issue-60424-async-return-inference, ↵bors-475/+549
r=cramertj extract expected return type for async fn generators Fixes #60424 cc @Centril, I know you've been eager to see this fixed. r? @cramertj
2019-10-03update ui testsGuillaume Gomez-1/+2
2019-10-03add regression test for #60218Niko Matsakis-0/+34
2019-10-03proc_macro: Add `Span::mixed_site` exposing `macro_rules` hygieneVadim Petrochenkov-35/+152
2019-10-03./x.py test --bless --compare-mode=nllNiko Matsakis-288/+258
2019-10-03--bless ui-fulldeps testsMazdak Farrokhzad-24/+210
2019-10-03plugin_registrary: use normal deprecation instead of hard coded warning.Mazdak Farrokhzad-259/+303
2019-10-03Deprecate `#![plugin]` and `#[plugin_registrar]`.Mazdak Farrokhzad-15/+107
2019-10-03Rollup merge of #64959 - davidtwco:issue-64252-self-type-help, ↵Mazdak Farrokhzad-0/+68
r=Centril,estebank syntax: improve parameter without type suggestions Fixes #64252. This PR improves the suggestions provided when function parameters do not have types: - A new suggestion is added for arbitrary self types, which suggests adding `self: ` before the type. - Existing suggestions are now provided when a `<` is found where a `:` was expected (previously only `,` and `)` or trait items), this gives suggestions in the case where the unnamed parameter type is generic in a free function. - The suggestion that a type name be provided (e.g. `fn foo(HashMap<u32>)` -> `fn foo(HashMap: TypeName<u32>)`) will no longer occur when a `<` was found instead of `:`. - The ident will not be used for recovery when a `<` was found instead of `:`. r? @Centril cc @estebank @yoshuawuyts
2019-10-03Rollup merge of #64931 - estebank:missing-param-ref, r=matthewjasper,CentrilMazdak Farrokhzad-20/+20
Reword E0392 slightly Make it clearer that a type or lifetime argument not being used can be fixed by referencing it in a struct's fields, not just using `PhathomData`. CC #53589.
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-04-27 08:09:28 +0000