[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: LuaJIT 2 clone-on-write for tables
- From: Alexander Gladysh <agladysh@...>
- Date: Wed, 19 Jan 2011 23:05:11 +0300
On Wed, Jan 19, 2011 at 22:05, Mike Pall <email@example.com> wrote:
> Alexander Gladysh wrote:
>> On Wed, Jan 19, 2011 at 21:46, Tony Finch <firstname.lastname@example.org> wrote:
>> > You can do that with a proxy table. Point __index at the table to be
>> > cloned, and when __newindex is called, copy everything to the proxy.
>> Thank you. As I noted in my original post, I'm aware of that solution.
>> My question is about LJ2 optimizations.
> Well, this is at the wrong level for a compiler optimization. How
> could it do better than that? It would have to do exactly the same
> things behind the curtains. It's not the compiler's business to
> handle stuff you can do at the user level with similar efficiency.
Ok, fair enough.
> [And I'm pretty sure it doesn't pay off either way. Rethink the
> whole thing and find easier ways to do what you're really trying
> to achieve. This sounds a lot like architecture astronautics.]
Quite possibly so.
Anyway, I need to get whole thing working first and then do some
profiling. I'm at the "get it working, no matter how" prototyping
stage so far.