You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the approach to allowing vectors on the wires is to have every wire carry a vector of the same length which is specified in the type parameter. This structuring has some downsides related to type checking and constructors of machines (see for example PR #112).
Specifying vector passing as part of the interface type, instead of as a type parameter for example, makes the hierarchy of interfaces clunky.
Finally, we would like to add support for vectors of different lengths along the wires.
The text was updated successfully, but these errors were encountered:
@tylerhanks, here is an issue caused by poor support for bundling. The approach you are thinking of involving Cospan(Set/Naturals)would be very helpful in improving support for wires that carry vectors.
Currently, the approach to allowing vectors on the wires is to have every wire carry a vector of the same length which is specified in the type parameter. This structuring has some downsides related to type checking and constructors of machines (see for example PR #112).
Specifying vector passing as part of the interface type, instead of as a type parameter for example, makes the hierarchy of interfaces clunky.
Finally, we would like to add support for vectors of different lengths along the wires.
The text was updated successfully, but these errors were encountered: