Ok, i think i understand, because of concurrent execution there may be pointer corruption
so no pointers pointing to the values inside the object are allowed, only pointers to objects themselves
method can return before the underlying async method is completed? and the memory for the pointer will be freed up/disposed before the operation on it is completed
And about the continious generation model, store all the data on what to generate next in every chunk's corner, and then check for it when continuing generation
Well how would you imagine it not doing so? I think you should store the noisemap somewhere and then generate chunks based on that and the coords of the chunk being generated