[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Proposal to enhance table.remove
- From: bil til <biltil52@...>
- Date: Sun, 11 Sep 2022 18:27:40 +0200
But if you want to see the "mil of returned elements", why then not
use the approach of Egor?
You do not need to encapsulate this in such an ingenious sub-func.
You could as well just first invoke table.unpack, to see the elements
which you want to remove.
And then in the next step invoike table.move(a1, f, e, t, a1) to strip
these elements from a1?
These are just 2 lua commands without any for loop in lua?
Am So., 11. Sept. 2022 um 18:04 Uhr schrieb Alexander Chernoskutov
> On 11.09.2022 20:41, bil til wrote:
> > (who really is interestend in seeing all the removed elements? I
> > think this would be quite a bizarre wish)
> Coincidently, this is exactly my use case and the reason why I had
> raised this discussion. So yea, the method of the core library should
> always strive to be generic and unassuming.
> With regards, Alex Ch