From 8600541d2199c80e4c42be01183cb3910ae994e9 Mon Sep 17 00:00:00 2001 From: Alex Gaynor Date: Sun, 14 Jul 2013 00:04:48 -0700 Subject: [PATCH] small rewrite --- docs/blog/type-specialized-instance-variables.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/blog/type-specialized-instance-variables.rst b/docs/blog/type-specialized-instance-variables.rst index 8a5e32e8e..da5eb53a1 100644 --- a/docs/blog/type-specialized-instance-variables.rst +++ b/docs/blog/type-specialized-instance-variables.rst @@ -6,10 +6,10 @@ Type Specialized Instance Variables In Topaz, like most other VMs, all objects are stored in what are called "boxes". Essentially that means when you have something like ``x = 5``, ``x`` is really a pointer to an object which contains ``5``, not the value ``5`` -itself. This is often a source of performance problems for VMs, this generates -more garbage for the GC to process and means that to access the value ``5`` -more memory dereferences are needed. Topaz's just-in-time compiler (JIT) is -often able to remove these allocations and memory dereferences in individual +itself. This is often a source of performance problems for VMs, because it +generates more garbage for the GC to process and means that to access the value +``5`` more memory dereferences are needed. Topaz's just-in-time compiler (JIT) +is often able to remove these allocations and memory dereferences in individual loops or functions, however it's not able to remove them in structures that stick around in memory, like objects.