Initial concurrent testing.
Bad, bad, bad. No. We're NEVER doing this again.
Load initial chunks on start, don't use such a sad seed resolution
(seconds)
go fmt ./...
Generate chunks concurrently.
That uses too much memory.
go fmt ./...
Only process 10 generation results per frame.
Update the chunk generation to respect priority.
Create a coords constant for the origin.
Several changes based on feedback. The callback forms of eachOffset seem
to be okay.
Fix a couple bugs + optimize.
Remove EveryOffset from the tests so that they pass again.
Merge pull request #168 from crazy2be/concurrent-generation

Concurrent generation