Allow Wire Labels to Dictate Name Inheritance in Bundles

[usrfrnly]

Not every bundle is linked to a Typedef. It would be very useful to automatically inherit the names of previously named wires into bundles.

Showing the Current and Proposed behavior for name inheritance in the bundle function

[wiebe@CARYA]

>A change in name is a change in type. It is nonsensical to say that you want to rename the type without changing the type because the name is part of the type.

I disagree. More importantly, the Assert Structural Type Match (you suggested) disagrees. Changing the name doesn't change the type!

I don't get why you claim a name change is a type change, and then suggest to check the type to see if it's the same after a name change. Those points contradict each other.

[srlm]

> More importantly, the Assert Structural Type Match (you suggested) disagrees. Changing the name doesn't change the type!

That's why the word "Structural" is in the node's name. It isn't just a type match. It is specifically looking at the type's structure, not the complete type. 

> I don't get why you claim a name change is a type change, and then suggest to check

> the type to see if it's the same after a name change. Those points contradict each other.

Again, it isn't a complete type check. It is only a structural type check. It is not checking to see if the names match. The node is explicitly leaving the type name out of the comparison.

[wiebe@CARYA]

Any reference you can point to?

You might be right, but I never heard anything like that. Not in LabVIEW, nor in any other programming language.

Anything else to back that up?

The wire label is in the type string, but it is ignored by 99% of functions that have anything to do with type.

Even if it's true in theory, practically this is largely ignored.

Regardless, why would this 'invalidate' the use for a node that changes the label and not the type?