Recommendations on avoiding range pipeline type hell

[Paul Backus]

On Saturday, 15 May 2021 at 13:46:57 UTC, Chris Piker wrote:
>
> Every time I slightly change the inputs to range2, then a 
> function that operates on *range3* output types blows up with a 
> helpful message similar to:
> [snip]

If you post your code (or at least a self-contained subset of it) 
someone can probably help you figure out where you're running 
into trouble. The error messages by themselves do not provide 
enough information--all I can say from them is, "you must be 
doing something wrong."