Gwern Branwen <[email protected]> writes: > Petr's technique of having a wrapper module import & re-export the otherwise > forbidden functions works, but it strikes me as kind of ugly. (I dislike > having extra source files doing obscure things to, it seems to me, work > around issues in a third-party tool.)
> Is there any hint option or technique we could use to suppress a particular > warning/error for a particular file? (In this case it'd be to suppress the > custom readFile/hGetContents errors for files x,y,& z.) But that would be wrong! HLint can already do that, but we have to ratify *instances* of the problem, not files. What you propose would disable the check for all of the file, and that's naturally undesirable. The fact the ratification mechanism is ugly is OK -- it we found ourselves ratifying too many things, it would mean that we are doing something wrong (i.e. that our policy is broken). Yours, Petr. _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
