From Thomas in the discussion of #6231:

Conceptually this feels like it belongs in a stat, but that would preclude it from being used together with other stats like in the examples above. However, I feel we did touch on the idea of having a stat_stack() at some point which would remove this downside

I'm lifting this out from that discussion to a separate issue as it blocks progress for #6231. Briefly, it would be good to have a stat, whose job it is to direct the serial computation of other stats. A 'composer' of stats, if you will. It would make re-implementing the position_connect() to a stat_connect() worthwhile. In addition, I think some other 'chains' of stats can be neat too, such as a typical stat (e.g. stat_bin) combined with more of a 'geometric' stat like ggforce::stat_link(), ggforce::stat_bezier() etc.