My understanding was that they ought to be the same. However, that didn't
seem to be the case. In my small example, where the plugin did work,
-fexpose-all-unfoldings did not.
On Sun, Oct 30, 2016 at 8:23 AM, Christiaan Baaij <
christiaan.ba...@gmail.com> wrote:
> One small question: what's the
Hi Takenobu
Thanks for writing this up. A small suggestion, for the box "Add a test
case" it might be good to add a reference to
https://ghc.haskell.org/trac/ghc/wiki/Building/RunningTests/Adding
Also it might be good to add something about the process of fixing doc
"bugs" and improving the doc.
One small question: what's the difference between adding INLINABLE
everywhere, and just compiling with -fexpose-all-unfoldings,
https://downloads.haskell.org/~ghc/latest/docs/html/users_guide/using-optimisation.html#ghc-flag--fexpose-all-unfoldings?
Is there any reason you couldn't use that flag as
Hi Ben, Joachim and devs,
I updated the following:
* page 7: update "committer flow" to "direct commit"
* page 9: add a simple diagram for the various ticket states
* page 10: update ghc-proposals flow
* page 13: correct "Arcanist"
* page 13: add "travis"
Here is Rev.2016-Oct-30:
GHC
