Catherine
Catherine
This would need to go through an RFC these days, and it also seems unlikely that the issue author still needs it.
This proposal, or my counter-proposal, would have to go through our [new RFC process](https://amaranth-lang.org/rfcs/) to be accepted. In general, the current system of defining pins should probably be scrapped entirely...
Looking over this again, there is basically no reason to ever have cases after `with m.Case()`; if you programmatically generate cases it's trivial to break from the loop, and if...
[Discussed](https://libera.irclog.whitequark.org/amaranth-lang/2023-02-06#1675703617-1675705826;) on the 2023-02-06 weekly meeting, with no conclusion reached beyond no one objecting to catching common cases of this issue without a full exhaustiveness check. In my view, there...
Now that `m.Default():` and `m.Case():` mean two separate (opposite, in fact) things, we can solve this by warning on any case that comes after `m.Default():`, without any of the complex...
No response from reporter for over two years.
So actually, when you instantiate a PLL, the toolchain creates a generated clock automatically. `create_generated_clock` is useful primarily in one case: when you have a clock *mux*. The SDC files...
Broadly speaking this is still desirable, but not a high priority; anyone who is willing to do the work of finding out which of the vendor toolchains accept the Yosys...
I'm going to close this issue since not much need has been expressed for this feature and as a consequence there are no current plans to add support it. Please...
This was reopened for the benefit of lkcl, who is no longer participating in the project. I think we can safely close this back as "no one (worth caring about)...