Hello Jules,

Friday, December 14, 2007, 12:21:30 PM, you wrote:

> PS we could give it a nice sensible name like hGetContents. We could
> renaming the existing hGetContents to 
> hUnsafeGetContentsDontUseThisUnlessYouHaveSpentThreeMonthsLearningGHCsExecutionSemanticsOrYouWillRegretIt

i have more advanced proposal - we should include in its name whole
paper on its semantics so anyone using it will be clearly warned.
moreover, any suggestion to use this function will automatically
include exact description of its caveats that is again The Right Thing
To Do :)


-- 
Best regards,
 Bulat                            mailto:[EMAIL PROTECTED]

_______________________________________________
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe

Reply via email to