Adventures in data-oriented design – Part 3c: External References

In the last installment of this series, we talked about handles/internal references in the Molecule Engine, and discussed their advantages over raw pointers and plain indices.

In a nutshell, handles are able to detect double-deletes, accesses to freed data, and cannot be accidentally freed – please read the previous blog post for all the details.

Continue reading


Adventures in data-oriented design – Part 3b: Internal References

As promised in the last blog post, today we are going to take a look at how Molecule handles internal references to data owned by some other system in the engine.

Continue reading