about summary refs log tree commit diff
path: root/src/test
AgeCommit message (Collapse)AuthorLines
2019-02-04Add testishitatsuyuki-0/+13
2019-02-03Fix testMatthias Einwag-1/+1
2019-02-03Apply review suggestions and fix testsMatthias Einwag-44/+132
2019-02-03Auto merge of #58081 - Centril:liballoc-2018, r=oli-obkbors-1/+1
Transition liballoc to Rust 2018 This transitions liballoc to Rust 2018 edition and applies relevant idiom lints. I also did a small bit of drive-by cleanup along the way. r? @oli-obk I started with liballoc since it seemed easiest. In particular, adding `edition = "2018"` to libcore gave me way too many errors due to stdsimd. Ideally we should be able to continue this crate-by-crate until all crates use 2018.
2019-02-03liballoc: alloc-extern-crates test needs --edition=2018Mazdak Farrokhzad-1/+1
2019-02-02Test behaviourClar Fon-4/+9
2019-02-02Update visibility of intermediate use items.David Wood-0/+35
Currently, the target of a use statement will be updated with the visibility of the use statement itself (if the use statement was visible). This commit ensures that if the path to the target item is via another use statement then that intermediate use statement will also have the visibility updated like the target. This silences incorrect `unreachable_pub` lints with inactionable suggestions.
2019-02-02rustfmt the testRalf Jung-30/+62
2019-02-01fix the build errorsLokathor-3/+6
2019-02-01const-int-wrapping.rs += wrapping_negLokathor-2/+5
2019-02-01const-int-overflowing.rs += overflowing_negLokathor-0/+6
2019-02-02Test alloca with #[repr(align(x))] on enumNiklas Fiekas-0/+36
2019-02-01Auto merge of #57937 - denzp:nvptx, r=nagisabors-0/+173
NVPTX target specification This change adds a built-in `nvptx64-nvidia-cuda` GPGPU no-std target specification and a basic PTX assembly smoke tests. The approach is taken here and the target spec is based on `ptx-linker`, a project started about 1.5 years ago. Key feature: bitcode object files being linked with LTO into the final module on the linker's side. Prior to this change, the linker used a `ld` linker-flavor, but I think, having the special CLI convention is a more reliable way. Questions about further progress on reliable CUDA workflow with Rust: 1. Is it possible to create a test suite `codegen-asm` to verify end-to-end integration with LLVM backend? 1. How would it be better to organise no-std `compile-fail` tests: add `#![no_std]` where possible and mark others as `ignore-nvptx` directive, or alternatively, introduce `compile-fail-no-std` test suite? 1. Can we have the `ptx-linker` eventually be integrated as `rls` or `clippy`? Hopefully, this should allow to statically link against LLVM used in Rust and get rid of the [current hacky solution](https://github.com/denzp/rustc-llvm-proxy). 1. Am I missing some methods from `rustc_codegen_ssa::back::linker::Linker` that can be useful for bitcode-only linking? Currently, there are no major public CUDA projects written in Rust I'm aware of, but I'm expecting to have a built-in target will create a solid foundation for further experiments and awesome crates. Related to #38789 Fixes #38787 Fixes #38786
2019-02-01Auto merge of #57978 - varkor:fix-irrefutable-integer-range-match, r=oli-obkbors-0/+7
Fix bug in integer range matching Fixes #57894.
2019-02-01Fix bug in integer range matchingvarkor-0/+7
2019-02-01update testRalf Jung-13/+13
2019-02-01add regression test for #57979Niko Matsakis-0/+42
2019-02-01don't try to get a DefId for a Def that doesn't have oneQuietMisdreavus-0/+8
2019-02-01Make the existential type errors a little bit more helpfulOliver Scherer-7/+7
2019-02-01Test more related casesOliver Scherer-0/+9
2019-02-01Restrict concrete types to equivalent typesOliver Scherer-16/+173
2019-02-01Generic type parameters are flexible even for existential typesOliver Scherer-86/+22
2019-02-01Test aller thingsOliver Scherer-0/+34
2019-02-01Test all the thingsOliver Scherer-24/+87
2019-02-01Be more permissive with required bounds on existential typesOliver Scherer-3/+8
2019-02-01Auto merge of #57586 - Aaron1011:feature/pub-priv-dep, r=petrochenkovbors-0/+110
Implement public/private dependency feature Implements https://github.com/rust-lang/rust/issues/44663 The core implementation is done - however, there are a few issues that still need to be resolved: - [x] The `EXTERNAL_PRIVATE_DEPENDENCY` lint currently does notthing when the `public_private_dependencies` is not enabled. Should mentioning the lint (in an `allow` or `deny` attribute) be an error if the feature is not enabled? (Resolved- the feature was removed) - [x] Crates with the name `core` and `std` are always marked public, without the need to explcitily specify them on the command line. Is this what we want to do? Do we want to allow`no_std`/`no_core` crates to explicitly control this in some way? (Resolved - private crates are now explicitly specified) - [x] Should I add additional UI tests? (Resolved - added more tests) - [x] Does it make sense to be able to allow/deny the `EXTERNAL_PRIVATE_DEPENDENCY` on an individual item? (Resolved - this is implemented)
2019-02-01Update tests for future-compat warning removalAaron Hill-13/+2
2019-02-01Test allowing individual struct fieldAaron Hill-0/+6
2019-02-01Replace --extern-public with --extern-privateAaron Hill-6/+5
2019-02-01Remove feature from testAaron Hill-1/+0
2019-02-01Rename external_private_dependency to exported_private_dependenciesAaron Hill-5/+5
2019-02-01Add test for 'std' crate being publicAaron Hill-0/+13
2019-02-01Clippy fixes, rename stuff to match RFCAaron Hill-6/+27
2019-02-01Improve UI testsAaron Hill-6/+32
2019-02-01Add UI testAaron Hill-0/+57
2019-02-01Auto merge of #57916 - Zoxc:incr-passes4, r=michaelwoeristerbors-10/+3
Misc performance tweaks r? @michaelwoerister
2019-02-01Fix image link in the settings menuGuillaume Gomez-1/+1
2019-02-01Auto merge of #58002 - oli-obk:deprecated_sugg, r=zackmdavisbors-0/+34
Add suggestions to deprecation lints Clippy used to do this suggestion, but the clippy lints happen after the deprecation lints so we ended up never seeing the structured suggestions.
2019-01-31rustdoc: wrap stability tags in colored spansAndy Russell-7/+15
2019-01-31Add more tests for #[repr(align(x))] on enumsNiklas Fiekas-8/+56
2019-01-31Add a forever unstable opt-out of const qualification checksOliver Scherer-0/+126
2019-01-31Auto merge of #57514 - michaelwoerister:xlto-tests, r=alexcrichtonbors-0/+69
compiletest: Support opt-in Clang-based run-make tests and use them for testing xLTO. Some cross-language run-make tests need a Clang compiler that matches the LLVM version of `rustc`. Since such a compiler usually isn't available these tests (marked with the `needs-matching-clang` directive) are ignored by default. For some CI jobs we do need these tests to run unconditionally though. In order to support this a `--force-clang-based-tests` flag is added to compiletest. If this flag is specified, `compiletest` will fail if it can't detect an appropriate version of Clang. @rust-lang/infra The PR doesn't yet enable the tests yet. Do you have any recommendation for which jobs to enable them? cc #57438 r? @alexcrichton
2019-01-31Add suggestion for duplicated import.David Wood-61/+301
This commit adds a suggestion when a import is duplicated (ie. the same name is used twice trying to import the same thing) to remove the second import.
2019-01-31Rollup merge of #58008 - matthewjasper:places-conflict-args, r=oli-obkMazdak Farrokhzad-0/+36
Pass correct arguments to places_conflict The borrow place *must* be a place that we track borrows for, otherwise we will likely ICE. Closes #57989
2019-01-31Rollup merge of #58007 - estebank:issue-58006, r=petrochenkovMazdak Farrokhzad-0/+24
Don't panic when accessing enum variant ctor using `Self` in match Fix #58006. r? @petrochenkov
2019-01-31Rollup merge of #57999 - jethrogb:jb/movbe-feature, r=alexcrichtonMazdak Farrokhzad-1/+2
Add MOVBE x86 CPU feature I have no idea if this is correct. I basically copied the ADX feature. I verified the feature is also called `movbe` in LLVM. I marked this to become stable immediately, as part of the RFC 2045. r? @alexcrichton
2019-01-31Rollup merge of #57008 - ↵Mazdak Farrokhzad-6/+54
Knium:misleading-try-adding-parentheses-in-match-with-comma, r=oli-obk suggest `|` when `,` founds in invalid match value Issue #54807 I get stuck on (what | how) I should implement...
2019-01-30Move privacy checking later in the pipeline and make some passes run in parallelJohn Kåre Alsaker-40/+59
2019-01-30Pass correct arguments to places_conflictMatthew Jasper-0/+36
The borrow place *must* be a place that we track borrows for, otherwise we will likely ICE.
2019-01-30Don't panic when accessing enum variant ctor using `Self` in matchEsteban Küber-0/+24
generated by cgit-pink 1.4.1-3-g733a5 (git 2.37.1) at 2026-02-28 11:54:14 +0000