Functionality already included via resizable Index Array function.
"Unbuild" would be the inverse of the "Build Array" function; the input would be an array, and the ouput would be the elements of the array. That way we can extract the items without having to go through an "Index Array" function for each element.
The "Index Array" function already does the inverse of "Build Array". You can expand the node to reveal as many output terminals as you want, and the "index" input terminals are not required. What other functionality are you looking for?
It amazes me how often you see code on the forums written the way Allen was thinking just because they didn't know the node was expandable. Why is that?
Is there some breakdown in communication? Is there not enough evidence of that in the help files to know? (The context help hints at it, but doesn't explictly state it, but the detailed help states it at the top.) Isn't this described in the tutorials? Or are people just not bothering to take tutorials or read the manual?
The related issue to this is when people do expand Index Array, but then go and explicitly wire constantst, 0, 1, 2, 3 .... to every index input without realizing they automatically start at zero and sequence from there by default.
> The related issue to this is when people do expand Index Array, but then go and explicitly wire constantst, 0, 1, 2, 3 .... to every index input without realizing they automatically start at zero and sequence from there by default.
To be fair, index array was not always resizeable, and there are probably some ancient examples that still don't utilize it. What we actually often see is the array-to-cluster-unbundle dance. ("A" instead of "B")
