Catherine

@gasche I have found one instance of an affected downstream package. Ironically, my own, ppx_deriving. I am not calling this a "regression" because it is merely exposing a bug that...

This is possibly related to https://github.com/ocaml/ocamlbuild/pull/140, https://github.com/ocaml/ocamlbuild/issues/166 and https://github.com/ocaml/ocamlbuild/issues/42...

@gasche BTW, since the CI is green now: I went ahead and, for master, disabled force pushes, and added a requirement that the build pass before a PR can be...

@gasche I've now installed, with --build-test, a fairly large amount of packages: ``` # Installed packages for 4.04.0+ocamlbuildtest: alcotest 0.7.2 Alcotest is a lightweight and colourful test framework. astring 0.8.3...

@gasche Can you go through https://github.com/ocaml/ocamlbuild/issues?q=is%3Aissue+is%3Aopen+label%3Atriage and state your opinion there? (The idea of the "triage" tag is that an issue for which a decision can and should be made,...

Sure, sounds good.

This all is broadly reasonable and in line with what I've been planning already. It is a very large change however, and I think we won't get around to it...

> Has anybody thought about adding clock frequency information to ClockDomains? Yes. This is a rather complex problem in situations where frequency can change at runtime. It should not be...

Reopened as requested by the author.

I've listed the challenges associated with the current clock domain system in [this conversation](https://libera.irclog.whitequark.org/amaranth-lang/2024-03-01#1709318917-1709327968;). To move this proposal forward, it will have to give an answer to these challenges, especially...