Discussion: Why is inet_addr in IO?

Johan Tibell johan.tibell at gmail.com
Sun Aug 31 17:38:19 UTC 2014


On Sun, Aug 31, 2014 at 5:47 PM, Gregory Collins <greg at gregorycollins.net>
wrote:

> Only if we run a deprecation cycle for at least one major version of
> network. Just removing a function breaks code for no reason and is
> user-hostile. It's important to give end users a warning that the function
> is going away and some time (12 months or more IMO) to fix their code,
> especially for packages that belong to the platform.
>

I like Java's policy of only deprecating (and often never removing)
functions that are actually dangerous to use (i.e. easy to use
incorrectly.)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.haskell.org/pipermail/libraries/attachments/20140831/ab296c66/attachment.html>


More information about the Libraries mailing list