Peter Lebbing

Seeing Alex's comment, maybe the changelog message should be tweaked a bit regarding > will properly set an exit code.

> I think we'll just have to test it. You'd hope that the simulators would detect they're running in a non-interactive environment. I'd like to know what this test shows!...

Perhaps we could tune it with `-fclash-hdlsyn` (we'd need to add `iverilog`).

We've released [v1.6.5](https://github.com/clash-lang/clash-compiler/releases/tag/v1.6.5), which includes a fix for this issue.

I made a mistake in the commit message of #2335. I accidentally wrote that #2335 closes this issue, but this is not the case. Please disregard the "commit that referenced...

I agree with Rowan, I think you should generally house your Clash design in a starter project. I am also not 100% sure if this is your question. That said,...

Thanks for taking the time to file an issue! We are painfully aware of this issue. Unfortunately, fixing it is impossible: a bug in Cabal prevents building Clash in Stack...

(Of course the issue is still valid and should remain open even though we can do nothing more towards the resolution. I made an error in judgement when I closed...

`docopt` has been in Stackage since [`nightly-2024-03-08`](https://www.stackage.org/nightly-2024-03-08/package/docopt-0.7.0.8), as Martijn and I are now the maintainers. But we thought we could not upload Clash because of the Cabal bug. Now when...

I know the process for getting on Stackage: you make a PR on `master` adding/uncommenting the packages. Sure. That's not the problem. I said _for getting back into an LTS_....