[m-dev.] referenced papers

Zoltan Somogyi zoltan.somogyi at runbox.com
Mon Aug 24 17:58:39 AEST 2015

On Mon, 24 Aug 2015 16:12:33 +1000, Peter Wang <novalazy at gmail.com> wrote:
> If anything, it should be a new git repository, e.g. "papers".

These references usually explain the design of a module. They play
the same role as compiler/notes/*, the two differences being (1) they are
often written by people outside the Mercury group, and (b) they are
postscript or pdf files, not text. However, neither seems reason enough
put people through more hoops to get at them.

While the mercury repo is of course usable for developers without
the papers in it, we eventually decided to move tests into the same repo,
after they were initially put into a different one. While the connection
is not nearly as strong in this case, I would prefer not to repeat
that process. I think the mercury repo should contain all the information
sources that Mercury developers may need to understand the Mercury
system. (Outside of basic background knowledge, of course.)


More information about the developers mailing list