Julian Oppermann

> Indeed, we could add removeOperation(), removeDependence(), and removeOperatorType() methods in the Problem class. This would give more control over the Problem and could be helpful for custom passes that...

> [...] to make the Problem class extensible from outside of CIRCT, which may be useful. Yes absolutely, OoT usability is super important. Let me pull in @7FM, who's also...

I've filed #7544, #7545, #7546 to track your proposals for the API extensions. I won't be able to work on this in the short term (traveling & preparing to move),...

> This was my idea to make it generic and extensible. I don't know if this is the best idea or the canonical way to do it, but I am...

> * I don't see why the cycle time isn't a property of the problem. Isn't it tightly related to the value of `incommingDelay`, `outgoingDelay` & `latency`? It is, but...

Thank you for putting this together! I would like to discuss and break down the changes into smaller parts (this is too big for a single PR anyways). The scheduler...

I'll look into alternatives for SSP. When is the next LLVM bump scheduled? The new, stricter checking is at runtime, correct? Could we temporarily disable the SSP tests? (SSP's main...

> I don't know SSP and don't know the distinction between auxiliary or not here - I'd have though one could do a variadic operand to all these ops which...