- User Since
- Aug 26 2014, 12:47 PM (139 w, 5 d)
Jan 22 2017
I mean, does it remove the definition so that it is definitely removed everywhere?
Oct 19 2016
Oct 18 2016
Aug 28 2016
What is the ticket number for this? Click "Edit revision" to add it, thanks.
For future reference: this feature was added to fix Trac #10083 (I think).
Currently the name of the warning flag in the documentation and in the implementation don't match.
Aug 27 2016
Missing changelog entry: docs/users_guide/8.2.1-notes.rst
Missing update to utils/mkUserGuidePart/Options/Misc.hs
Changelog entry is missing. This would go in docs/users_guide/8.2.1-notes.rst normally.
Jul 24 2016
Jul 22 2016
Just some final remarks. After that I think we can push this (before any merge problems arise), and perhaps continue in a new Diff.
Jul 21 2016
Jul 20 2016
What's with the Template Haskell in the test? Is that necessary?
Nice and small patch.
Jul 19 2016
Still looking good. Some small comments.
Jul 18 2016
This looks ok, after a quick scan, except for one mistake.
In FrontendPluginUser, you're passing in a frontend plugin with -fplugin instead of with --frontend (see https://downloads.haskell.org/~ghc/master/users-guide/extending_ghc.html#frontend-plugins). Is that intentional?
This is good.
Jul 13 2016
perf.haskell.org show now performance regressions.
Jul 11 2016
Compile-time performance differences:
- -67% 'bytes allocated' for T12227 (8.0.1 even looped on this one)
- -3% 'max_bytes_used' for T3294
- +3% 'bytes allocated' for T3294 (I don't know why, but I'm ignoring it)
The new flags need to be mentioned in utils/mkUserGuidePart/Options/CompilerDebugging.hs as well (sorry for not alerting you earlier).
Jul 9 2016
How about this
Jul 8 2016
This looks ok, but it needs some documentation. See point 6 and 7 of https://ghc.haskell.org/trac/ghc/wiki/WorkingConventions/AddingFeatures#HowtocontributeanewfeaturetoGHC.
Jul 7 2016
This looks ok to me, but I'd like a sign off from someone on the CLC.
Jul 1 2016
Jun 30 2016
Jun 29 2016
Jun 28 2016
I tried this, but you end up with a very confusing intertwining of stdout and stderr.
I pushed the above patch, although T7037 still fails occasionally.
Maybe the testsuite driver should ignore extra_ways for run_commands. What do you think?