15

Could somebody explain to me why table.unpack() returns the first table element only when it is used in a function call with additional parameters after table.unpack()?

Here is some demo code:

local a = {1,2,3,4,5}
print("Test", table.unpack(a))   -- prints "Test 1 2 3 4 5"
print(table.unpack(a), "Test")   -- prints "1 Test"

I don't understand why the second line just prints 1 Test. I'd expect it to print 1 2 3 4 5 Test. Can somebody explain this behaviour? I'd also be interested in how I can make the second call to print 1 2 3 4 5 Test.

Yu Hao
  • 119,891
  • 44
  • 235
  • 294
Andreas
  • 9,245
  • 9
  • 49
  • 97

2 Answers2

20

table.unpack returns multiple values. The defined behavior in that case is that if it is not the last one in a list of expressions then all but the first returned value will be discarded.

From the book:

Lua always adjusts the number of results from a function to the circumstances of the call. When we call a function as a statement, Lua discards all of its results. When we use a call as an expression, Lua keeps only the first result. We get all results only when the call is the last (or the only) expression in a list of expressions.

As a workaround you can append the rest of the arguments to the table and make the table the last argument that way.

ntki
  • 2,149
  • 1
  • 16
  • 19
4

table.unpack() is returning the same thing in either case, but in the second case Lua is only expecting one value so it isn't going to turn it into multiple arguments. When it is the last argument Lua is ok with it turning into multiple arguments.

Bartek Banachewicz
  • 38,596
  • 7
  • 91
  • 135
chicks
  • 2,393
  • 3
  • 24
  • 40
  • Thanks. So I guess there is no way to make the second call return "1 2 3 4 5 Test"? – Andreas Sep 07 '15 at 13:26
  • @Andreas *We get all results only when the call is the last (or the only) expression in a list of expressions.* sounds pretty clear, in the other answer. – Bartek Banachewicz Sep 07 '15 at 13:27
  • Yes, I know, I just asked because maybe there was a trick or something to workaround this behaviour :) – Andreas Sep 07 '15 at 13:28
  • @Andreas: appending to the table before unpacking it as one might work for you. – ntki Sep 07 '15 at 13:29