LabVIEW
Converting Empty Array to .NET object
Yeah, a .NET array of "Empty" size is .... well... a pointer to a memory location of "non-existant" 
In fact, you need no memory to store an array of <insert datatype here> with length = 0 so, why would you return anything other than an error when asking to allocate Zero memory?
It sounds a lot like giving a squirrel zero nuts, asking the squirrel to bury those nuts and then asking the critter to remember where it did not bury the nuts you did not give it!
Arrays itself are not really immutable but not resizable just as in Java. If you need resizable arrays you have to use object types derived from the List interface or something similar.
Problem with conversions like this is that there is not a single target type but really many different possible types. .Net Arrays is the most direct corresponding type but being non resizable a array of 0 elements makes no sense.
Just as an extra tidbit I think I know why there is this difference. LabVIEW knows internally of two types of empty arrays and strings. One is simply a NULL handle and the other is a handle with the count member set to 0.
The reason for this is optimization. An array of 1'000'000 empty strings consumes about 4 MB of memory when using NULL for the empty strings and about at least 12MB of memory for when using explicit empty handles (in reality even more since every handle also consumes some extra bookkeeping overhead of about 8 to 16 bytes per handle).
Initially when the VI is loaded the empty array in the control is initialized to a NULL handle internally. When you edit the control and add an element a real handle is allocated to strore this element. When you then delete that element the handle is not really changed other than updating the count parameter to indicate that 0 elements are there. That is a trivial operation with virtually zero cost while physically deallocating the handle is pretty expensive as the memory manager is getting invoked and potentially that could cause a whole bunch of extra operations too.
Now almost everywhere in LabVIEW a NULL handle is simply considered an empty array (or string) but this function seems to make a difference. This could be an oversight but it is even more likely that this is actually intended in the function that is getting used here, as .Net doesn't have the same behaviour of considereing a NULL object automatically as an empty object. I agree that in this specific case it could be considered as equal but in many other cases where the function that is used in this VI may get used, this is likely not the case.
