The addition of new fields on prototype-side are propagated into children due the current lookup semantics/rules.
Hence, it's needed to change the __index metamethod to take into account if the current selector is updated on clone-side. If it is indeed updated, even being nil, no further lookups on prototype-side could be performed.
The addition of new fields on prototype-side are propagated into children due the current lookup semantics/rules.
Hence, it's needed to change the __index metamethod to take into account if the current selector is updated on clone-side. If it is indeed updated, even being nil, no further lookups on prototype-side could be performed.