Marek Materzok
Marek Materzok
I think that optimizations like this should be done after the full implementation of exceptions is there, so that we can get a better picture of how they affect both...
> But we are loosing consistency. I think we are actually gaining consistency, as: * Keyword arguments allows to define functions just like method definitions. * The filter function can...
> This is an expected and intended consequence of the design. (There is no way to implement View, in general, with multiple signals due owing to the existence of union...
> Effectively this issue is asking for a decoupling of the Signals in the source code and the VCD lines, which isn't something that we can easily, or without a...
> How invasive would a workaround be? Still needs to be explored. We collect signals used in debugging after all Elaboratables are constructed, but before they are passed to the...
Thanks for the info, we will test it soon.
@whitequark This is almost what we need. Almost, because we rely on the `traces` feature of `write_vcd` to automatically generate a nice `.gtkw` file. This allows us to quickly view...
@whitequark This looks good enough, thank you.
@whitequark Sure, I'll report back when it's done. I'm optimistic with regard to #957 - we sure welcome more type strictness.
We found a weird issue with VCD writing. Sometimes having signals with identical names leads to an error: ```python from amaranth import * from amaranth.sim import * class Lol(Elaboratable): def...