Just to be clear, is WASH beyond redemption, or would it be worth reviving again? If so, why?
Cheers, Darren On 2013-05-05 1:48 PM, "Alberto G. Corona" <[email protected]> wrote: > The case of WASH is a pity. Architecturally It was more advanced that many > recent haskell web frameworks. The package would have been a success with > little changes in the DSL syntax. > > I suspect that there are many outstanding packages with great ideas > abandoned, like WASH > > > > 2013/5/5 Brandon Allbery <[email protected]> > >> On Sun, May 5, 2013 at 7:55 AM, Raphael Gaschignard >> <[email protected]>wrote: >> >>> Forgive me if I'm wrong, but I feel like I've seen such "suggestions" in >>> GHC errors before. >>> >>> If so, does that mean there's some sort of mechanism in the compiler >>> already in place for such error recognition? Like some simple pattern >>> stuff? If not, I think that it might not be bad to consider this stuff >>> (misused packaged, changed semantics that create compiler errors), and to >>> put something into place for future modifications. This could make it a lot >>> easier to deal with unmaintained code. >>> >> >> There's some very limited capability now; the GHC folks are tossing >> around ideas for something more general like that. >> >> >> -- >> brandon s allbery kf8nh sine nomine >> associates >> [email protected] >> [email protected] >> unix, openafs, kerberos, infrastructure, xmonad >> http://sinenomine.net >> >> _______________________________________________ >> Haskell-Cafe mailing list >> [email protected] >> http://www.haskell.org/mailman/listinfo/haskell-cafe >> >> > > > -- > Alberto. > > _______________________________________________ > Haskell-Cafe mailing list > [email protected] > http://www.haskell.org/mailman/listinfo/haskell-cafe > >
_______________________________________________ Haskell-Cafe mailing list [email protected] http://www.haskell.org/mailman/listinfo/haskell-cafe
