Here is the current status of the 2013.4.0.0 proposal.
*Outstanding Issues*
We have a few decisions outstanding, and I'd like to have these decided by
Nov. 23 (one week).
- fgl - waiting to hear if Ivan will have new version ready in time.
- aeson / dlist - there are serveral options -- I'l
We seem to have several interlocking decisions to make about *aeson* and
*dlist* in the platform:
*Background:*
*let me know if I got any of this wrong*
- There is clear agreement to have *aeson* in the platform.
- *aeson* 0.6.2.1 would require *dlist* & *blaze-builder* to be added.
- Th
There's currently an issue with Alex happy when they're built with clang
cpp rather Than GCC cpp which some folks are trying to hammer out I think.
I think it's a problem in Alex 3.1.2 but not 3.1.0.
Either way: assuming that bug gets sorted out, making sure Haskell platform
has a fresher Alex /
looks like theres a candidate patch for the alex issue by Nick Partridge
https://github.com/simonmar/alex/pull/37
On Sun, Nov 17, 2013 at 3:25 PM, Carter Schonwald <
carter.schonw...@gmail.com> wrote:
> There's currently an issue with Alex happy when they're built with clang
> cpp rather Than GC
On Sun, Nov 17, 2013 at 12:25 PM, Carter Schonwald <
carter.schonw...@gmail.com> wrote:
> There's currently an issue with Alex happy when they're built with clang
> cpp rather Than GCC cpp which some folks are trying to hammer out I think.
> I think it's a problem in Alex 3.1.2 but not 3.1.0.
S
good point, pardon any confusion.
On Mon, Nov 18, 2013 at 12:49 AM, Mark Lentczner
wrote:
> On Sun, Nov 17, 2013 at 12:25 PM, Carter Schonwald <
> carter.schonw...@gmail.com> wrote:
>
>> There's currently an issue with Alex happy when they're built with clang
>> cpp rather Than GCC cpp which som
