Can you elaborate regardless? It introduces 1 more type, removes the vararg type and some functions that deals with var args. The end result are less lua functions and fewer exceptions to remember.
In a way we have 2 fundamental types already. The entire table library assumes that the table passed is treated as an array type. This separation has grown more since table.pack and table.unpack was introduced. Ipairs work on arrays and pairs work on everything else, now there're only pairs.
For those of us who have used Lua for a long time and understand the differences between arrays and tables, a change like this is something new we would have to learn. So in that sense not changing anything is more simple than learning something new. Is that what you mean?
Maybe I should have used a different subject in the email. I honestly don't expect this to be implemented in Lua, but I would definitely be interested in a change like this. I'm also wondering if for instance the introduction of [] as a constructor would cause issues with other syntax (backwards compatibility aside) or if these changes could make the C implementation more difficult.
