Rachit Nigam

Just pinging this thread to say that I've also run into this problem and would find this PR really useful when merged

Awesome! I think we should merge this since `main` on Calyx already has the required changes. I think after this release of the Calyx compiler, we should discuss a better...

Agreed with @cgyurgyik! I think we should try getting something working first and worry about optimizing the encoding later on. @jiahanxie353 answers to your questions: > What should we do...

No, it’s complaining that compilation generated a group that is not used by the calyx control program. This means you generated the group but didn’t add it to the control...

LGTM on my end! @cgyurgyik any final C++ comments?

Filament used to do this by passing a mutable `DiagnosticsReporter` responsible for accumulating errors and reporting them after a pass has completed. We can do something similar but have to...

@sgpthomas I really like this approach! One tricky thing is making sure that the error reporting code does not assume that bail outs will occur. For example, if a particular...

I like the idea of primary and secondary paths. `fud` also has a similar notion with the `Path.also_do_path` method which specifies how a particular step requires a sequence of actions...

Is there still top-level discussion needed for this issue? If we have a resolution, can we mark this as "available" instead?

I like this idea! It is in the spirit of #1603. The idea is that Calyx is purely responsible for defining the computational interface of the component and something else...