- Pipelines being large expressions that are hard to line-step into.
- Visibility of intermediate results.
- Localizing operations (in time and code position) in the presence of lazy evaluation semantics.
In this screencast we demonstrate how to mitigate the impact of all of these issues and quickly and effectively debug pipelined code.
The example code is here.