On 26 Jun 2018, at 13:13, Kenneth Lorber <firstname.lastname@example.org
On Jun 23, 2018, at 8:57 AM, Andrew Gierth <email@example.com> wrote:
"Kenneth" == Kenneth Lorber <firstname.lastname@example.org> writes:
Kenneth> require() seems to silently accept extra arguments. Is this a
Pretty much every function accepts and silently ignores extra arguments,
unless the function itself bothers to check for them and throw an
Thanks, and after a little source diving you are correct, but that's not quite the reply I was looking for.
Is there some reason this is a language feature? Some use-case I don't see? (If so, why is there the occasional check for extra arguments?)
Is it documented somewhere I missed?
Is there any reason not to add checks for extra arguments? If it's performance, it could be available as a compile time option.
I'm working for an implementation for 5.3.4. If there's any interest please let me know or I'll just quietly add it to my copy and stop bothering the list about it.
To me it is about flexibility, multiple return values, and the ability to only take what is needed. Eg:
Without a bunch of locals. Why would you even want to limit that and make it an error? It takes flexibility away.
For example: take OpenResty, it uses a lot of those extra checks and it's a pita. See this code for example:
The last argument “socket options” must be a table, not even `nil` is accepted. Hence in the calling code it requires an if-then construct.
So be careful what you wish for with those checks.