Felix Klein

I would use it [here](https://github.com/bittide/bittide-hardware/compare/staging...hitl-topologies#diff-ffba1bb951968297f0a0bf02d7b31bd54f347dba6b054dec31d990152baf29e1R64), but the currently used workaround is also sufficient. It is required to use the `Resize` class in that case.

That is a general problem with naming. If instances are unique, then names turn obsolete, but as soon as multiple of them are around, having some way to properly name...

The reason I consider `setName` to be non-user friendly is that it requires to have explicit access to the references of the respective ILAs. Consider the following example. ```haskell module...

`setNameVec` would indeed be a solution for this particular problem and I currently cannot imagine where it could break or still be insufficient. `setNameVec` would get a vector of names...

>Why did we change `dfold`, but introduced an additional function for `smap`? The primary argument was that `smap` may be used by beginners, which may be overwhelmed by the extended...

The `feedback` function definitely is broken. I tried to create a `DSignal` version of `register`, as I can't use `register` in a `DSignal` environment and `delayedI` causes a type mismatch...

> The, it is this ! in the data definition that cancels out all the infos (maybe you know more how it works than me). Interesting observation. I wasn't aware...

> I cannot really run this code, because LH gives me too many errors before the p3... Oh, I'm sry, I should have added more context on my setup. Here's...

Thanks to @nikivazou we also got the reproducer working with 791567f. I updated the code above accordingly. After the update the code now produces multiple ``` **** LIQUID: ERROR *************************************************************...

@AlecsFerra yes that is basically what I want, but I need `unFin` inlined here such that I can use it in the `Num` instance later on. However, adding a `{-@...