Re: Tables vs closures for representing objects (and JITability)

[Mark Hamburg <mark@...>]

You also need to figure out (e.g., through testing though sometimes reasoning will give you a decent answer) what actually matters for performance. For example, you are going with closures to avoid self.* lookups but that's a lot of memory allocations per object which will impact object creation (and collection) time, impact memory locality for object data, and impact overall memory footprint. There can be big differences in performance based on which cache you manage to fit in.

Mark