Leaderboard

As far as breaking VIs when such a condition is detected, I need to give it some thought. I know I've been guilty of leaving one particular race in production code simply because if the race was ever to be "lost" it really wouldn't matter but fixing the race would be a very risky and time consuming bit of work. The corollary to that is if the outcome doesn't matter is it really a race condition or more an undefined order of execution? I'd tend to argue the later, but could still see some small bit of misguided merit to the race side of that coin. Regardless of what action is taken, I think the possibility of having the compiler detect even the most primitive of such conditions a great advancement. Nice work. Given how easy it is to leverage LabVIEW to make parallel processes I think educating users into pointing out resulting races a very good step into making LabVIEW a more mature development environment.