[enhancement] Improve ScopedVerifyProcEquivalence to track token dependencies & support conditional send
allight opened this issue · comments
What's hard to do? (limit 100 words)
ScopedVerifyProcEquivalence won't verify that procs maintain token dependency semantics and has no support for multiple conditional sends (even if they are mutually exclusive) on a single channel. This limits somewhat the sorts of procs that can be validated.
Current best alternative workaround (limit 100 words)
None
Your view of the "best case XLS enhancement" (limit 100 words)
Support these use cases