Excerpts from nicolas.pouillard's message of Wed Mar 25 20:16:22 +0100 2009:
> Excerpts from Jean-Philippe Bernardy's message of Wed Mar 25 20:05:02 +0100 
> 2009:
> > 
> > Yep, I think the first step would be to modify data-accessor-template
> > to generate type signatures. That might remove a good 50 warnings.
> 
> This is almost done, the version 0.2.1 does that but there is a bug in case
> of parameterized data types (I think that Yi is unaffected).
> I've submitted a patch and 0.2.2 should be OK.

data-accessor-template 0.2.1.1 is now available on hackage and yi build fines
with it.

> 
> > 
> > -- JP
> > 
> > On Wed, Mar 25, 2009 at 7:56 PM, Gwern Branwen <gwe...@gmail.com> wrote:
> > > On Wed, Mar 25, 2009 at 2:18 PM, Kevin Ballard <kball...@gmail.com> wrote:
> > >>
> > >> The number of warnings that a clean build of yi triggers is rather
> > >> frightening. It also makes it quite difficult to figure out if a change
> > >> I've
> > >> made has introduced any new warnings. I would like to suggest that 
> > >> anybody
> > >> capable of doing so should start trying to fix these warnings, with the
> > >> eventual goal of `runghc Setup build` printing zero warnings (though,
> > >> given
> > >> the current number, that may not be attainable). I will certainly try to
> > >> do
> > >> my part, but as a relative newcomer to yi and to Haskell in general, I
> > >> don't
> > >> know if I'll be able to understand them well enough to be sure of any
> > >> fixes.
> > >> Does anybody else have an opinion on this?
> > >
> > > It's a good goal, but many of them are out of our power - like the
> > > defaulting messages caused by the derive-generated code. And I think a
> > > number of them are there just because some code is experimental and not 
> > > yet
> > >  cleaned up - there a -Wall cleanup could be detrimental.
> > >
> > > --
> > > gwern
> > 
> 

-- 
Nicolas Pouillard

--~--~---------~--~----~------------~-------~--~----~
Yi development mailing list
yi-devel@googlegroups.com
http://groups.google.com/group/yi-devel
-~----------~----~----~----~------~----~------~--~---

Reply via email to