BUG: Labelled array constant vs build array vs Bundle (array loses label) (LV2019)

[Yamaeda]

So, this is a fairly common design, right?

[avogadro5]

I don't think the language makes guarantees about what the wire label will be in situations like this so I wouldn't classify it as a bug.

[altenbach]

You could also do the following to ensure that the label survives...

Note that the wire after the build has no name when  probed. it's a bit a can of worms. What if you would concatenate two arrays (same problem:  no wire name, even if both input arrays are named the same!)

In my best practices, I always wire a cluster constant with proper element names to the top of the bundle operation if I later want to do anything "by name".

[Yamaeda]

If i have an advanced testcase i typedef a cluster, but usually i just create constants or wire inital wires to a bundle. I mean i could wire the constant and then use a Bundle by name, but it was just stuff like that i was trying to avoid.

I had this situation i thought "Why to i type cast the array, why not simply Build array and it'll be a little cleaner"

Btw, you can't Type cast a Path in this way, you must use Coerce to type. Hmm, i'll use that on Programmers also, it looks a little nicer.

Still i consider it a bug!

[drjdpowell]

Not a "bug", in that NI doesn't really promise to support this kind of dynamic name use and they would probably suggest you make a cluster constant to define names.  BUT, I personally think it is a valuable use case and NI should make some effort to support it.