On Fri, Apr 17, 2015 at 9:56 AM Nikita Karetnikov
I'm reminded of SPJs usual request for a wiki page *with details* discussing pros/cons of all the proposals for new GHC features. Might it be time to start such a page? (Of course this is not meant to imply any particular *rush* per se, but this is obviously becoming a growing concern in the community.)
I think it must be the first step. Otherwise, it's hard to evaluate the proposals. It would be great if both designs could be compared side by side. I'd suggest to create a file in the commercial haskell repo (so that authors of both designs (and others) could freely edit it) with a list of things that people care about, which should be as specific as possible. For example:
| FPComplete | Well-Typed | --------------------------------------------------------------- Design document | https://... | https://... |
Does this design protect from these attacks?
| FPComplete | Well-Typed | -------------------------------------------------------------- Attack1 | yes | no | Attack1Comment | because of so and so | because of so and so | Attack2 | no | yes | Attack2Comment | because of so and so | because of so and so | Attack3 | no | no | Attack3Comment | because of so and so | because of so and so | ...
Features:
| | FPComplete | Well-Typed | --|---------------------------------------------------------- 1 |Allows for third-party mirrors | yes | yes | 2 |Comment regarding 1 | ... | ... |
Estimated effort:
| | FPComplete | Well-Typed | --|----------------------------------------------------------------- 1 | Tools required | git, ... | ... | 2 | Tools that need to be changed | ... | ... | 3 | Time required for 2 (hours) | ... | ... | 4 | Size of changes required for 2 (LOC) | ... | ... |
Possibly with comments, too.
This is a great idea, thank you both for raising it. I was discussing something similar with others in a text chat earlier this morning. I've gone ahead and put together a page to cover this discussion: https://github.com/commercialhaskell/commercialhaskell/blob/master/proposal/... The document definitely needs more work, this is just meant to get the ball rolling. As usual with the commercialhaskell repo, if anyone wants edit access, just request it on the issue tracker. Or most likely, send a PR and you'll get a commit bit almost magically ;) Michael