Assertion: Expected data check // A review from a user's question

Thanks Ben for your feedback.

I have another problem related to this assertion.

Turns out the logic I’m testing has a 2 deep pipeline.

So when $rose(go) occurred twice, the payload was also updated twice before ready == 1.

When ready ==1, the payload had 2nd data but ready==1 with out was expecting the 1st data.

So I got a FAIL in simulator.

How to update the assertion to add a pipeline or FIFO so that the payload data gets

properly matched up with corresponding ready ?

Also, maybe make the FIFO/pipeline generic enough to have an N-deep and store more levels.