Lets assume, we would double, triple, quadruple, etc. Bobs world and stack these copies on top of each other. Bob would never notice, as long as each copy is just a “shallow” copy, meaning that each movement in the fundamental domain (the original world) is mirrored in the copies. In this case, we would have a covering space of Bobs world, and the original world would be the base space.
You get the same story with async functions. Swift has a whole separate library for dealing with async operations on collections, because the methods on the existing collections can’t be generic to support both synchronous and asynchronous versions. There’s no such thing as re-async.
，详情可参考91视频
The cynical opportunities of ‘Epic Fury’
for (const chunk of chunks) {
lda #$ba ; For phase 3, move the corners down