Data dependent method calling

[lekcyjna123]

We have currently concept of single caller methods (#416, #425). Such methods allow us to add condition in ready signal which depends from input argument. Such conditions are only supported in single caller methods, because when there are two or more callers there is a risk that we end up with combinational cycle. Goal of this PR is to extend data dependent readiness of methods to multi caller methods.

Current implementation of transactron assume that readiness signal is constant for the whole cycle. So we use it to calculate runnable signal for each transaction. When ready signal depend from data we can decided after scheduling a transaction to execution that method isn't ready. This cause change in runnable and an another transaction can be chosen to execution, which data will be potentially accepted by method, so the ready will be high one more time and the whole story will repeat.

Solution which I propose in this PR is to calculate data dependent readiness before scheduling the transaction, so that we already know that method will accept data from this transaction. The old ready signal is used as global readiness for the whole method for backward compatibility.

Additionally I modified types in method_uses to be more strict. Instead of ValueLike only Record is accepted. This allow to properly type input argument for the user_ready_function.

[tilk]

Solution which I propose in this PR is to calculate data dependent readiness before scheduling the transaction, so that we already know that method will accept data from this transaction.

I find this explanation very unintuitive. "Before" and "after" doesn't matter for combinatorial logic; only thing that exists are data dependencies. What you are doing, in actuality, is generating separate circuits for the readiness condition for each calling transaction. This relaxes the previous restriction on ready signals, but at the cost of a (potentially small) increase in circuit size.

The idea seems sound; I'll review the PR later.

[tilk]

This change is pretty cool actually, but some cleanups are required.

[tilk]

The old ready signal is used as global readiness for the whole method for backward compatibility.

This is not just backward compatibility. Both things have a different performance characteristic: there is only one combinatorial circuit generating the old ready signal, but the ready function is instantiated for each transaction calling the method.

[tilk]

Left some minor comments.

[tilk]

Merged without a second review.