[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: [proposal] Type metatables per environment
- From: Miles Bader <miles@...>
- Date: Thu, 22 Dec 2011 10:29:00 +0900
Patrick Rapin <firstname.lastname@example.org> writes:
> My proposal is the following: provided it is possible, why not limit
> the metatable scope to the environment of the current function?
> Even better, I could imagine that the type metatables could be placed
> in the metatable of _ENV and manipulated from there.
Soooo what are the details? How does the compiler implement this?
How would it impact performance?
Do you mean that, for instance, OP_GETTABLE would need a 4th argument
to pass in _ENV? ... and _every_ indexing operation (maybe the most
common operation in Lua bytecode) would then need to get and pass in
Cat is power. Cat is peace.