Right now, cursors are implemented by having an internal type that manually implements a Future state machine and has a lot of machinery to handle tracking state between calling getMore and reading from a cached chunk. I think this could be simplified by having a spawned task for the cursor that's dedicated to executing getMore in a loop, sending the results down a channel, and performing cursor cleanup once the channel is closed.