Review GPCE Draft about next-700-module-systems HOT 7 CLOSED

If you're going to create issues, you ought to assign them!

from next-700-module-systems.

This is now done. But weirdly, I can't close it myself. Why not?

from next-700-module-systems.

@JacquesCarette and @WolframKahl

As per JC's advice, I have avoided incorporating the many new design decisions of the prototype since the paper was submitted. However, I have updated the obsolete portions so that the paper is not mostly useless wrt to the current prototype implementation.

Please take a look at the PDF; commit 810d10f.

from next-700-module-systems.

Is the Paper0.org up to date? I've noticed typos, that I can easily enough fix myself, but I don't want to edit a stale file.

from next-700-module-systems.

Also, why are there no references in the generated PDF? There's a lot of stuff to edit - grammar mistakes, nonsensical sentences, overly chatty sentences, overly editorial sentences [without evidence to back up the opinion]. And those are just the ones I caught, @WolframKahl might catch others.

from next-700-module-systems.

For future reference, always assume the repo contains up to date content. Merge conflicts are acceptable.

Feedback, either on the PDF or org-mode or even in an arbitrary text file or scrap of paper is appreciated.

It is a small PDF, you may not have found them where you expected them to be, but they are there.

A hardcopy can be provided if you would like one.

from next-700-module-systems.

Done. It makes sense to open a separate one for Wolfram to do.

from next-700-module-systems.