diff options
author | domdom <domdom@users.noreply.github.com> | 2017-07-12 09:39:10 +1000 |
---|---|---|
committer | Alec Thomas <alec@swapoff.org> | 2017-08-01 13:03:51 +1000 |
commit | 6389b1f91598c99d85e56356fb57d9f4683071d8 (patch) | |
tree | 0b228af1128646f1c1554ed7ede07a17c65fc1cd | |
parent | de3fd13d72d82b507469a3ed8798d483df6bc5d1 (diff) |
Fix typo
lyout -> layout
-rw-r--r-- | CHANGES.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -2,7 +2,7 @@ ## 2014-03-02 - 1.0.0alpha1 - Cache coherence + breaking changes -EntityX has switched to a more cache-friendly memory layout for components. This is achieved by requiring the use of `assign<Component>(arg0, arg1, ...)` and removing `assign(component)`. This allows EntityX to explicitly control the layout of components. The current lyout algorithm reserves space for components in chunks (8192 by default). +EntityX has switched to a more cache-friendly memory layout for components. This is achieved by requiring the use of `assign<Component>(arg0, arg1, ...)` and removing `assign(component)`. This allows EntityX to explicitly control the layout of components. The current layout algorithm reserves space for components in chunks (8192 by default). This change also necessitated a move away from the use of `shared_ptr<>` for components, which I had never been that pleased with anyway. Replacing it is a very lightweight `ComponentHandle<C>` smart pointer. This checks for validity of the entity associated with the component, and validity of the component itself. It also allows future iterations of EntityX to do even more interesting things with memory layout if desirable. |