+1 on making aggregators responsible for calling `setNextReader` on their children. Maybe we can leave it as-is for now (I think it's ok) and do it as part of another issue/PR?