[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: New to-be-closed variable list implementation question
- From: Roberto Ierusalimschy <roberto@...>
- Date: Fri, 5 Mar 2021 13:31:45 -0300
> I (also) have a question related to this commit:
> https://github.com/lua/lua/commit/4e47f81188d37e29027158b76271d02a781242e2
> . Aside from performance reasons, is there anything stopping us from
> storing the 'to-be-closed flag' in e.g. an unused pointer or tt_ bit
> inside the stack value and keeping the old StackValue definition?
> Keeping a count of such variables and the index of the last of them in
> the state could address performance issues in some use common cases...
Aside from performance reasons, everything in programming could be quite
different :-) But I have not understood your suggestion. Once we close
the last of them, how to find the next one?
-- Roberto
