Can the join CHOP's 0 inputs error be optional?

I use the join chop in replicated networks where each replicant has a chop of n length.
It’s very useful for combining arbitrary lengths of consistent channels into 1 large block of data to do operations on efficiently.


When no inputs are connected to the join CHOP it gives an error. Obviously one can choose to ignore the errors as they don’t actually hurt anything, but for me I pursue errors in my network vigorously and having false positives floating about all the time is a bit distracting and sometimes masks real issues.

Wondering if there’s a more specific reason why the join chop behaves like this when the merge chop does not?


Would also love a way to write some sort of condition that if met, doesn’t let a particular node throw that error!