[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: Definition of table.insert
- From: GrayFace <sergroj@...>
- Date: Sat, 08 Jan 2011 16:22:17 +0600
On 08.01.2011 14:34, David Kastrup wrote:
Just to get it straight: can it ever make sense to insert nil using
'Should' that not rather throw an error, because any table.insert()
after that could have undefined behavior?
Isn't it pretty much guaranteed you'd never want to do |table.
I think it should be defined as a straight noop not changing the table
at all, ever.
What's the use case?
IMO, it's good the way it is. Less checks mean more code and
Sergey Rozhenko mailto:email@example.com