<div dir="ltr">Hi devs,<br><br>How about putting it here every release? :<br>  <a href="https://downloads.haskell.org/~ghc/latest/docs/html/">https://downloads.haskell.org/~ghc/latest/docs/html/</a>  or<br>  <a href="https://downloads.haskell.org/~ghc/latest/docs/">https://downloads.haskell.org/~ghc/latest/docs/</a><br><br>`core-spec.pdf` will be helpful.<br>But generating it in Windows is a bit complicated :)<br><br>Regards,<br>Takenobu<br><br></div><div class="gmail_extra"><br><div class="gmail_quote">2017-03-14 7:57 GMT+09:00 Ben Gamari <span dir="ltr"><<a href="mailto:ben@well-typed.com" target="_blank">ben@well-typed.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello everyone,<br>
<br>
Currently there is a typeset copy of the Core specification in the GHC<br>
repository. This means any time someone changes the specification the<br>
repository grows by around 300kB. While this isn't the end of the<br>
world, it's generally considered bad form to put generated files under<br>
version control.<br>
<br>
Of course, the tools required to typeset the specification (ott and<br>
LaTeX) are non-trivial to install, so there is considerable convenience<br>
that comes from having a typeset version readily available.<br>
<br>
I suggest that we remove the PDF from the repository but instead I can<br>
start including it in my nightly documentation builds. Any objections?<br>
<br>
Cheers,<br>
<br>
- Ben<br>
<br>______________________________<wbr>_________________<br>
ghc-devs mailing list<br>
<a href="mailto:ghc-devs@haskell.org">ghc-devs@haskell.org</a><br>
<a href="http://mail.haskell.org/cgi-bin/mailman/listinfo/ghc-devs" rel="noreferrer" target="_blank">http://mail.haskell.org/cgi-<wbr>bin/mailman/listinfo/ghc-devs</a><br>
<br></blockquote></div><br></div>