h1. inspect.lua This function transform any Lua table into a human-readable representation of that table. The objective here is human understanding (i.e. for debugging), not serialization or compactness. h1. Examples of use "Array-like" tables are rendered horizontally:
inspect({1,2,3,4}) == "<1>{ 1, 2, 3, 4 }"
"dictionary-like" tables are rendered with one element per line:
inspect({a=1,b=2}) == [[<1>{
a = 1,
b = 2
}]]
The keys will be sorted alphanumerically when possible.
"Hybrid" tables will have the array part on the first line, and the dictionary part just below them:
inspect({1,2,3,a=1,b=2}) == [[<1>{ 1, 2, 3,
a = 1,
b = 2
}]]
Tables can be nested, and will be indented with two spaces per level.
inspect({a={b=2}}) = [[<1>{
a = <2>{
b = 2
}
}]]
By default, @inspect@ will stop rendering at a depth of 4 levels. When that point is reached, it will just return @{...}@ :
local t5 = {a = {b = {c = {d = {e = 5}}}}}
inspect(t5) == [[<1>{
a = <2>{
b = <3>{
c = <4>{
d = {...}
}
}
}
}]]
You can increase/decrease the max depth with the second parameter:
inspect(t5, 2) == [[<1>{
a = <2>{
b = {...}
}
}]])
inspect(t5, 7) == [[<1>{
a = <2>{
b = <3>{
c = <4>{
d = <5>{
e = 5
}
}
}
}
}]])
Functions, userdata and threads are simply rendered as @
inspect({ f = print, ud = some_user_data, thread = a_thread} ) == [[{
f = ,
u = ,
thread =
}]])
If the table has a metatable, inspect will include it at the end, in a special field called @
inspect(setmetatable({a=1}, {b=2}) == [[<1>{
a = 1
= <2>{
b = 2
}
}]])
You may have noticed that all tables are preceded by an @