Unwired output of "Bundle" and "Bundle By Name" should show broken arrow

[Samuel_James]

If the output terminal of "Bundle" or "Bundle By Name" is unwired the vi should should show broken arrow.

You can ask me the question why?

Consider a scenario of the below picture. As soon I wire all the input terminals and input cluster of "Bundle By Name" the vi is in run mode. There is nothing wrong in that, But if I forget to wire the output terminal of bundle by name...... You know what will happen. If it happens in a sub vi of a very big project it is very hard to debug, More over there is no use in any scenario to leave the output of the Bundle By Name unwired, 

In the above picture the vi is in run mode when unbundle by name output is unwired

In the above picture the vi shows broken arrow when "bundle by name" output is unwired

[Darin.K]

When I am doing real programming using Visual Studio, I have a Debug Mode as well as a Release Mode.  LV could benefit (IMO) from something similar.  This type of thing could be an error in Release Mode, but not in Debug Mode.  And heck, it would make it easier to disable debugging.

At any rate I would probably rather get a "hint" than a broken run arrow.  One possibility is to Bleach Dead Code.

[dthor]

Yes, I really liked altenbach's Bleach Dead Code idea. In my opinion, his Idea fully encapsulates this idea - it gives a visual notification that code is not going to be used, which the OP could interpret as "oh no I forgot to wire that output" and others (like myself) could use in their crazy-overnight-I'm-just-going-to-try-anything-and-everything coding sessions.

[X.]

I usually don't turn on the warnings because they tell me about things I don't care (the loop index is hidden - sure, but why is it floating around in the first place?) and does not tell me about things I would care about (like those unconnected unbunbdle outputs we are discussing here). The bleach dead code idea is neat but unless you stumble upon it on the diagram, you won't know about it.

The beauty of the configurable warnings (looked at like a "search" window) would be that you could check for specific issues at any time during development - or not.

My 2 cts.