Eliminate redundant bounds checks

Create issue
Issue #42 resolved
David Williams created an issue

I've recently added getVoxel() to replace getVoxelAt() as the new version provides the ability to skip bounds checks. I should go through the code and ensure that bounds checks are indeed being skipped wherever possible.

Comments (2)

  1. David Williams reporter
    • changed version to 0.3

    This should be done for 0.3 to make sure that the supporting changes I've made actually work :-)

  2. Log in to comment