Gabriel Scherer

Is the fact that join points are forbidden an observation about the current state of what we handle, or something that is part of your internal specification for Value_rec_compiler and...

My current thinking: I like that this PR improves behavior in some weird corner cases, the behavior when it works well is rather elegant. But I also wouldn't fully trust...

@xavierleroy I wonder if you have an opinion and would be willing to "shepherd" the PR -- make a general decision and maybe ask someone to review it. (I thought...

@dra27: > However, having moved `Dynlink` into the Standard Library, this opens the possibility of using it for the toplevel. That's presently not possible because `ocaml` is part of the...

Note for myself: the repro case needs to be a updated because the previous location and syntax is deprecated. ```coq Require Import Stdlib.derive.Derive. Derive foo in (foo = 1) as...

I'm happy to change the codebase to rewrite more, but given that there is no centralized handling of "paths" in the compiler (they are built as strings in many places)...

(Maybe this is good to be merged?)

Pragmatically, we need to agree on *something* to be able to start making decisions and thus serve the purpose that the Language Committee was designed for. It was already not...

Some more pointed feedback. > The first question concerns the motivations for introducing a CoI policy. From the public discussion of the committee on its mailing list, the CoI policy...

> I was surprised some times to learn in private such ties from academic contributors that were not known publicly within the community. [...] (Disclosure: I was proposed such funding...