Re: incorrect "error" signaled by type(value), when the argument value is nil

[Javier Guerra Giraldez <javier@...>]

On Tue, 7 Sept 2021 at 04:48, Paul Ducklin <pducklin@outlook.com> wrote:
>
> So my natural reading of your notation would be that call(a,) and call(a) ought to be equivalent, in the same way that {a} and {a,} are equivalent.

funny, I actually expected that `{f(),}` would result in a single
element table no matter the number of return values of `f()`.  I had
to try it to check and was surprised to find that it expands to all
results, just like `{f()}`.



-- 
Javier