rust-libp2p/swarm/tests/ui/fail/out_event_deprecation.stderr

error: use of deprecated constant `out_event_renamed_to_to_swarm::_w`: The `out_event` attribute has been renamed to `to_swarm`.
 --> tests/ui/fail/out_event_deprecation.rs:6:13
  |
6 | #[behaviour(out_event = "FooEvent", prelude = "libp2p_swarm::derive_prelude")]
  |             ^^^^^^^^^
  |
note: the lint level is defined here
 --> tests/ui/fail/out_event_deprecation.rs:1:9
  |
1 | #![deny(warnings)] // Ensure the warnings we produce surface as errors.
  |         ^^^^^^^^
  = note: `#[deny(deprecated)]` implied by `#[deny(warnings)]`
refactor(swarm-derive): improve warning message Pull-Request: #3921. 2023-05-14 15:12:06 +02:00			error: use of deprecated constant `out_event_renamed_to_to_swarm::_w`: The `out_event` attribute has been renamed to `to_swarm`.
			`--> tests/ui/fail/out_event_deprecation.rs:6:13`
feat(swarm): rename associated types for message passing Previously, the associated types on `NetworkBehaviour` and `ConnectionHandler` carried generic names like `InEvent` and `OutEvent`. These names are _correct_ in that `OutEvent`s are passed out and `InEvent`s are passed in but they don't help users understand how these types are used. In theory, a `ConnectionHandler` could be used separately from `NetworkBehaviour`s but that is highly unlikely. Thus, we rename these associated types to indicate, where the message is going to be sent to: - `NetworkBehaviour::OutEvent` is renamed to `ToSwarm`: It describes the message(s) a `NetworkBehaviour` can emit to the `Swarm`. The user is going to receive those in `SwarmEvent::Behaviour`. - `ConnectionHandler::InEvent` is renamed to `FromBehaviour`: It describes the message(s) a `ConnectionHandler` can receive from its behaviour via `ConnectionHandler::on_swarm_event`. The `NetworkBehaviour` can send it via the `ToSwarm::NotifyHandler` command. - `ConnectionHandler::OutEvent` is renamed to `ToBehaviour`: It describes the message(s) a `ConnectionHandler` can send back to the behaviour via the now also renamed `ConnectionHandlerEvent::NotifyBehaviour` (previously `ConnectionHandlerEvent::Custom`) Resolves: #2854. Pull-Request: #3848. 2023-05-14 12:58:08 +02:00			`\|`
refactor(swarm-derive): improve warning message Pull-Request: #3921. 2023-05-14 15:12:06 +02:00			`6 \| #[behaviour(out_event = "FooEvent", prelude = "libp2p_swarm::derive_prelude")]`
			`\| ^^^^^^^^^`
feat(swarm): rename associated types for message passing Previously, the associated types on `NetworkBehaviour` and `ConnectionHandler` carried generic names like `InEvent` and `OutEvent`. These names are _correct_ in that `OutEvent`s are passed out and `InEvent`s are passed in but they don't help users understand how these types are used. In theory, a `ConnectionHandler` could be used separately from `NetworkBehaviour`s but that is highly unlikely. Thus, we rename these associated types to indicate, where the message is going to be sent to: - `NetworkBehaviour::OutEvent` is renamed to `ToSwarm`: It describes the message(s) a `NetworkBehaviour` can emit to the `Swarm`. The user is going to receive those in `SwarmEvent::Behaviour`. - `ConnectionHandler::InEvent` is renamed to `FromBehaviour`: It describes the message(s) a `ConnectionHandler` can receive from its behaviour via `ConnectionHandler::on_swarm_event`. The `NetworkBehaviour` can send it via the `ToSwarm::NotifyHandler` command. - `ConnectionHandler::OutEvent` is renamed to `ToBehaviour`: It describes the message(s) a `ConnectionHandler` can send back to the behaviour via the now also renamed `ConnectionHandlerEvent::NotifyBehaviour` (previously `ConnectionHandlerEvent::Custom`) Resolves: #2854. Pull-Request: #3848. 2023-05-14 12:58:08 +02:00			`\|`
			`note: the lint level is defined here`
			`--> tests/ui/fail/out_event_deprecation.rs:1:9`
			`\|`
			`1 \| #![deny(warnings)] // Ensure the warnings we produce surface as errors.`
			`\| ^^^^^^^^`
			= note: `#[deny(deprecated)]` implied by `#[deny(warnings)]`