rust/tests/ui/privacy/private-in-public-warn.stderr

340 lines
14 KiB
Plaintext
Raw Normal View History

2018-08-08 07:28:26 -05:00
error: private type `types::Priv` in public interface (error E0446)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:15:5
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub type Alias = Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
2022-09-18 10:55:36 -05:00
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
2020-01-22 17:57:38 -06:00
note: the lint level is defined here
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:5:9
2018-08-08 07:28:26 -05:00
|
LL | #![deny(private_in_public)]
| ^^^^^^^^^^^^^^^^^
error: private type `types::Priv` in public interface (error E0446)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:18:12
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | V1(Priv),
2018-08-08 07:28:26 -05:00
| ^^^^
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `types::Priv` in public interface (error E0446)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:20:14
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | V2 { field: Priv },
2018-08-08 07:28:26 -05:00
| ^^^^^^^^^^^
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `types::Priv` in public interface (error E0446)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:24:9
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | const C: Priv = Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error[E0446]: private type `types::Priv` in public interface
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:26:9
2018-08-08 07:28:26 -05:00
|
LL | struct Priv;
2022-02-13 09:27:59 -06:00
| ----------- `types::Priv` declared as private
2018-08-08 07:28:26 -05:00
...
2019-03-09 06:03:44 -06:00
LL | type Alias = Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^ can't leak private type
2018-08-08 07:28:26 -05:00
error: private type `types::Priv` in public interface (error E0446)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:27:9
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | fn f1(arg: Priv) {}
Use smaller def span for functions Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata.
2020-08-12 16:02:14 -05:00
| ^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `types::Priv` in public interface (error E0446)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:29:9
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | fn f2() -> Priv { panic!() }
Use smaller def span for functions Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata.
2020-08-12 16:02:14 -05:00
| ^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `types::Priv` in public interface (error E0446)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:33:9
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub static ES: Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `types::Priv` in public interface (error E0446)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:35:9
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub fn ef1(arg: Priv);
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `types::Priv` in public interface (error E0446)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:37:9
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub fn ef2() -> Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error[E0446]: private type `types::Priv` in public interface
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:41:9
2018-08-08 07:28:26 -05:00
|
LL | struct Priv;
2022-02-13 09:27:59 -06:00
| ----------- `types::Priv` declared as private
2018-08-08 07:28:26 -05:00
...
2019-03-09 06:03:44 -06:00
LL | type Alias = Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^ can't leak private type
2018-08-08 07:28:26 -05:00
error: private trait `traits::PrivTr` in public interface (error E0445)
2018-12-25 09:56:47 -06:00
--> $DIR/private-in-public-warn.rs:50:5
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub type Alias<T: PrivTr> = T;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `traits::PrivTr` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:53:5
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub trait Tr1: PrivTr {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `traits::PrivTr` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:55:5
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub trait Tr2<T: PrivTr> {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `traits::PrivTr` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:58:9
|
LL | type Alias: PrivTr;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `traits::PrivTr` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:61:9
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | fn f<T: PrivTr>(arg: T) {}
Use smaller def span for functions Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata.
2020-08-12 16:02:14 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `traits::PrivTr` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:64:5
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | impl<T: PrivTr> Pub<T> {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `traits_where::PrivTr` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:74:5
2018-08-08 07:28:26 -05:00
|
LL | pub type Alias<T> where T: PrivTr = T;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `traits_where::PrivTr` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:78:5
2018-08-08 07:28:26 -05:00
|
LL | pub trait Tr2<T> where T: PrivTr {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `traits_where::PrivTr` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:82:9
2018-08-08 07:28:26 -05:00
|
LL | fn f<T>(arg: T) where T: PrivTr {}
Use smaller def span for functions Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata.
2020-08-12 16:02:14 -05:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `traits_where::PrivTr` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:86:5
2018-08-08 07:28:26 -05:00
|
LL | impl<T> Pub<T> where T: PrivTr {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `generics::PrivTr<generics::Pub>` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:98:5
2018-08-08 07:28:26 -05:00
|
LL | pub trait Tr1: PrivTr<Pub> {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `generics::Priv` in public interface (error E0446)
--> $DIR/private-in-public-warn.rs:101:5
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub trait Tr2: PubTr<Priv> {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `generics::Priv` in public interface (error E0446)
--> $DIR/private-in-public-warn.rs:103:5
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub trait Tr3: PubTr<[Priv; 1]> {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `generics::Priv` in public interface (error E0446)
--> $DIR/private-in-public-warn.rs:105:5
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub trait Tr4: PubTr<Pub<Priv>> {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error[E0446]: private type `impls::Priv` in public interface
--> $DIR/private-in-public-warn.rs:132:9
2018-08-08 07:28:26 -05:00
|
LL | struct Priv;
2022-02-13 09:27:59 -06:00
| ----------- `impls::Priv` declared as private
2018-08-08 07:28:26 -05:00
...
2019-03-09 06:03:44 -06:00
LL | type Alias = Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^ can't leak private type
2018-08-08 07:28:26 -05:00
error: private type `aliases_pub::Priv` in public interface (error E0446)
--> $DIR/private-in-public-warn.rs:203:9
2018-08-08 07:28:26 -05:00
|
2019-03-09 06:03:44 -06:00
LL | pub fn f(arg: Priv) {}
Use smaller def span for functions Currently, the def span of a funtion encompasses the entire function signature and body. However, this is usually unnecessarily verbose - when we are pointing at an entire function in a diagnostic, we almost always want to point at the signature. The actual contents of the body tends to be irrelevant to the diagnostic we are emitting, and just takes up additional screen space. This commit changes the `def_span` of all function items (freestanding functions, `impl`-block methods, and `trait`-block methods) to be the span of the signature. For example, the function ```rust pub fn foo<T>(val: T) -> T { val } ``` now has a `def_span` corresponding to `pub fn foo<T>(val: T) -> T` (everything before the opening curly brace). Trait methods without a body have a `def_span` which includes the trailing semicolon. For example: ```rust trait Foo { fn bar(); }``` the function definition `Foo::bar` has a `def_span` of `fn bar();` This makes our diagnostic output much shorter, and emphasizes information that is relevant to whatever diagnostic we are reporting. We continue to use the full span (including the body) in a few of places: * MIR building uses the full span when building source scopes. * 'Outlives suggestions' use the full span to sort the diagnostics being emitted. * The `#[rustc_on_unimplemented(enclosing_scope="in this scope")]` attribute points the entire scope body. * The 'unconditional recursion' lint uses the full span to show additional context for the recursive call. All of these cases work only with local items, so we don't need to add anything extra to crate metadata.
2020-08-12 16:02:14 -05:00
| ^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error[E0446]: private type `aliases_pub::Priv` in public interface
--> $DIR/private-in-public-warn.rs:207:9
2018-08-08 07:28:26 -05:00
|
LL | struct Priv;
2022-02-13 09:27:59 -06:00
| ----------- `aliases_pub::Priv` declared as private
2018-08-08 07:28:26 -05:00
...
2019-03-09 06:03:44 -06:00
LL | type Check = Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^ can't leak private type
2018-08-08 07:28:26 -05:00
error[E0446]: private type `aliases_pub::Priv` in public interface
--> $DIR/private-in-public-warn.rs:210:9
2018-08-08 07:28:26 -05:00
|
LL | struct Priv;
2022-02-13 09:27:59 -06:00
| ----------- `aliases_pub::Priv` declared as private
2018-08-08 07:28:26 -05:00
...
2019-03-09 06:03:44 -06:00
LL | type Check = Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^ can't leak private type
2018-08-08 07:28:26 -05:00
error[E0446]: private type `aliases_pub::Priv` in public interface
--> $DIR/private-in-public-warn.rs:213:9
2018-08-08 07:28:26 -05:00
|
LL | struct Priv;
2022-02-13 09:27:59 -06:00
| ----------- `aliases_pub::Priv` declared as private
2018-08-08 07:28:26 -05:00
...
2019-03-09 06:03:44 -06:00
LL | type Check = Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^ can't leak private type
2018-08-08 07:28:26 -05:00
error[E0446]: private type `aliases_pub::Priv` in public interface
--> $DIR/private-in-public-warn.rs:216:9
|
LL | struct Priv;
2022-02-13 09:27:59 -06:00
| ----------- `aliases_pub::Priv` declared as private
...
2019-03-09 06:03:44 -06:00
LL | type Check = Priv;
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^ can't leak private type
error: private trait `PrivTr1` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:246:5
2018-08-08 07:28:26 -05:00
|
LL | pub trait Tr1: PrivUseAliasTr {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private trait `PrivTr1<Priv2>` in public interface (error E0445)
--> $DIR/private-in-public-warn.rs:249:5
2018-08-08 07:28:26 -05:00
|
LL | pub trait Tr2: PrivUseAliasTr<PrivAlias> {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
error: private type `Priv2` in public interface (error E0446)
--> $DIR/private-in-public-warn.rs:249:5
2018-08-08 07:28:26 -05:00
|
LL | pub trait Tr2: PrivUseAliasTr<PrivAlias> {}
2022-02-13 09:27:59 -06:00
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2018-08-08 07:28:26 -05:00
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #34537 <https://github.com/rust-lang/rust/issues/34537>
warning: bounds on generic parameters are not enforced in type aliases
--> $DIR/private-in-public-warn.rs:50:23
|
2019-03-09 06:03:44 -06:00
LL | pub type Alias<T: PrivTr> = T;
| ^^^^^^
|
= note: `#[warn(type_alias_bounds)]` on by default
help: the bound will not be checked when the type alias is used, and should be removed
|
LL - pub type Alias<T: PrivTr> = T;
LL + pub type Alias<T> = T;
2022-06-08 12:34:57 -05:00
|
warning: where clauses are not enforced in type aliases
--> $DIR/private-in-public-warn.rs:74:29
|
LL | pub type Alias<T> where T: PrivTr = T;
| ^^^^^^^^^
|
help: the clause will not be checked when the type alias is used, and should be removed
|
LL - pub type Alias<T> where T: PrivTr = T;
LL + pub type Alias<T> = T;
2022-06-08 12:34:57 -05:00
|
error: aborting due to 34 previous errors; 2 warnings emitted
2018-08-08 07:28:26 -05:00
For more information about this error, try `rustc --explain E0446`.