User | Kudos |
---|---|
6 | |
6 | |
3 | |
2 | |
2 |
This idea is somewhat related to the following ideas, but not a duplicate:
In my opinion, if a wire has a single source, (but no sink), it should not be broken, because it has a valid data type and no illegal constructs (such as e.g. a wire without source, a wire with two sources, a wire between two incompatible terminals, etc).
Of course one way around it are the JKI Wire-Nuts, but they require a trip to the palette. 😄
My suggestion is to simply treat them as valid, but dead code and Ctrl+b should not remove them initially (maybe only after entering ctrl+b twice in a row?). They should have the appearance of the correct data type, but should be bleached as suggested here for all other dead code. This will make it easy to tack down a few wires for later code completion and they will be easier to tell apart based on the appearance.
Currently, everything looks black with a few hints based on wire width. This idea will also make the truly broken wires easier to find because they will still be black.
Discussion points:
Maybe it should be possible to probe dangling wires during debugging.
If a dangling error wire is connected to an error output, automatic error handling should be suppressed (similarly to wiring to e.g. a structure boundary only)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.