c0a93aa7a4
# Objective > System chaining is a confusing name: it implies the ability to construct non-linear graphs, and suggests a sense of system ordering that is only incidentally true. Instead, it actually works by passing data from one system to the next, much like the pipe operator. > In the accepted [stageless RFC](https://github.com/bevyengine/rfcs/blob/main/rfcs/45-stageless.md), this concept is renamed to piping, and "system chaining" is used to construct groups of systems with ordering dependencies between them. Fixes #6225. ## Changelog System chaining has been renamed to system piping to improve clarity (and free up the name for new ordering APIs). ## Migration Guide The `.chain(handler_system)` method on systems is now `.pipe(handler_system)`. The `IntoChainSystem` trait is now `IntoPipeSystem`, and the `ChainSystem` struct is now `PipeSystem`. |
||
|---|---|---|
| .. | ||
| ambiguity_detection.rs | ||
| executor_parallel.rs | ||
| executor.rs | ||
| graph_utils.rs | ||
| label.rs | ||
| mod.rs | ||
| run_criteria.rs | ||
| stage.rs | ||
| state.rs | ||
| system_container.rs | ||
| system_descriptor.rs | ||
| system_set.rs | ||