about summary refs log tree commit diff
path: root/src/test/ui/privacy
AgeCommit message (Collapse)AuthorLines
2019-04-18hide `--explain` hint if error has no extended infoAndy Russell-7/+7
2019-04-14Properly parse '--extern-private' with name and pathAaron Hill-1/+1
2019-03-15rustc: pass Option<&Substs> and Namespace around in ty::item_path.Eduard-Mihai Burtescu-10/+10
2019-03-15rustc: support impl's in PrintCx::parameterized.Eduard-Mihai Burtescu-6/+6
2019-03-11Update testsVadim Petrochenkov-243/+243
2019-03-06Split up privacy checking so privacy_access_levels only does computations ↵John Kåre Alsaker-18/+18
required for AccessLevels
2019-02-07Auto merge of #58010 - Zoxc:parallel-passes, r=michaelwoeristerbors-25/+44
Move privacy checking later in the pipeline and make some passes run in parallel r? @michaelwoerister
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-4/+4
2019-02-01Add test for 'std' crate being publicAaron Hill-0/+13
2019-02-01Clippy fixes, rename stuff to match RFCAaron Hill-6/+6
2019-02-01Improve UI testsAaron Hill-6/+32
2019-02-01Add UI testAaron Hill-0/+57
2019-01-30Move privacy checking later in the pipeline and make some passes run in parallelJohn Kåre Alsaker-25/+44
2019-01-18privacy: Account for associated existential typesVadim Petrochenkov-6/+33
2019-01-14Rollup merge of #57556 - petrochenkov:privexist, r=arielb1Mazdak Farrokhzad-0/+15
privacy: Fix private-in-public check for existential types Fixes https://github.com/rust-lang/rust/issues/53546 (regression from https://github.com/rust-lang/rust/pull/56878) r? @arielb1
2019-01-13privacy: Fix private-in-public check for existential typesVadim Petrochenkov-0/+15
2019-01-09clarify resolve typo suggestionAndy Russell-6/+30
Include the kind of the binding that we're suggesting, and use a structured suggestion.
2019-01-05privacy: Mark everything in a header of a reachable impl as reachableVadim Petrochenkov-8/+28
2019-01-05privacy: Fix regression in impl reachabilityVadim Petrochenkov-0/+17
2019-01-01Address review commentsVadim Petrochenkov-19/+19
Say "trait" instead of "type" in diagnostics for `dyn Trait`
2019-01-01privacy: Use common `DefId` visiting infra for all privacy visitorsVadim Petrochenkov-14/+140
2018-12-25Remove licensesMark Rousskov-787/+337
2018-12-24make non_camel_case_types an early lintAndy Russell-10/+8
2018-12-20Stabilize `Rc`, `Arc` and `Pin` as method receiversMichael Hewson-17/+31
This lets you write methods using `self: Rc<Self>`, `self: Arc<Self>`, `self: Pin<&mut Self>`, `self: Pin<Box<Self>`, and other combinations involving `Pin` and another stdlib receiver type, without needing the `arbitrary_self_types`. Other user-created receiver types can be used, but they still require the feature flag to use. This is implemented by introducing a new trait, `Receiver`, which the method receiver's type must implement if the `arbitrary_self_types` feature is not enabled. To keep composed receiver types such as `&Arc<Self>` unstable, the receiver type is also required to implement `Deref<Target=Self>` when the feature flag is not enabled. This lets you use `self: Rc<Self>` and `self: Arc<Self>` in stable Rust, which was not allowed previously. It was agreed that they would be stabilized in #55786. `self: Pin<&Self>` and other pinned receiver types do not require the `arbitrary_self_types` feature, but they cannot be used on stable because `Pin` still requires the `pin` feature.
2018-11-25resolve: Prohibit relative paths in visibilities on 2018 editionVadim Petrochenkov-0/+29
2018-11-18resolve: Avoid sentence breaks in diagnosticsVadim Petrochenkov-4/+4
2018-11-18resolve: Check resolution consistency for import paths and multi-segment ↵Vadim Petrochenkov-0/+18
macro paths
2018-11-07Removed `#[rustc_error]` from tests that are all `// compile-pass`.Felix S. Klock II-15/+3
I also added `// skip-codegen` to each one, to address potential concerns that this change would otherwise slow down our test suite spending time generating code for files that are really just meant to be checks of compiler diagnostics. (However, I will say: My preference is to not use `// skip-codegen` if one can avoid it. We can use all the testing of how we drive LLVM that we can get...) (Updated post rebase.)
2018-10-28Rollup merge of #55199 - oli-obk:instance_printing, r=davidtwcokennytm-8/+8
Impl items have generics
2018-10-28resolve: More precise spans for privacy errorsVadim Petrochenkov-150/+143
2018-10-26Update testsOliver Scherer-8/+8
2018-10-02Nest the `impl Trait` existential item inside the return typeOliver Schneider-16/+2
2018-08-14Merged migrated compile-fail tests and ui tests. Fixes #46841.David Wood-0/+5250