Catherine
Catherine
I'm not sure why we need any of the above solutions. I propose the following, which ensures that the build script is always run with `/bin/sh`: ```patch diff --git a/amaranth/build/run.py...
Obsoleted by #1104.
@alanvgreen https://github.com/amaranth-lang/amaranth/pull/628#issuecomment-1414802510
There has not been a consensus on this proposal, and due to the complexity and impact it would have to go through our [new RFC process](https://amaranth-lang.org/rfcs/) to be accepted. In...
This has been designed and is now being implemented in RFCs 1 and 2: - https://github.com/amaranth-lang/amaranth/issues/748 - https://github.com/amaranth-lang/amaranth/issues/872
Support for capturing assertions in CXXRTL is about to land upstream as part of https://github.com/YosysHQ/yosys/pull/4128. Amaranth will require modification to emit `$check` cell from `Assert` statements once that PR lands....
Support for this feature has been accepted via [RFC 50](https://amaranth-lang.org/rfcs/0050-print.html) and implementation is tracked in issue #1186.
RFC https://github.com/amaranth-lang/rfcs/pull/61. Superseded by #1244.
I think what we can do is warn on m.If(x == (1 & y)): where the shape of `x` isn't `unsigned(1)`, with the suppression being: m.If(x == (1 & y).bool()):...
This issue is resolved by the combination of #1232 (which allows visualizing delta cycles in Python simulations) and #1213 (which is a meta-issue that thoroughly improves our simulation semantics).