String.Concat are based off of the .net class,
string. The .net class has several overloads for both
Depending on what arguments you feed into the nodes, the system makes its best guess as to what you want to happen. The problem is that the UI doesn't necessarily match what is happening in the backend.
For instance, both the
String.Concat nodes ask for
string in the
string0 input. This tells the user that you need to put in a list of strings. But, in reality you can put a list of strings, a single string, even a multi-dimensional list of strings. The node will make its best guess as to which method to actually call. For instance, if you feed the node a mix of individual strings and lists, the node will call the method that has a list as the parameter and not the one that uses individual strings. The node will never mix and match the method calls. It is too hard to predict that this is what the user wants. We don't surface each overload node because there are just too many. We tried to pick the one that we thought users would use the most.
Hope this makes sense