Proposal: Deprecate decodeUtf8

Jon Purdy evincarofautumn at
Thu Aug 18 19:58:11 UTC 2016

On Thu, Aug 18, 2016 at 10:19 AM, David Feuer <david.feuer at> wrote:
> Being the disruptive sort.... What if we DEPRECATE it for a cycle and then
> change its type? Almost all code that is no longer correct will fail to
> typecheck.

The “almost” is the worrying part. ;)

But I would second deprecation followed by a change in type or name,
as I prefer not to use exceptions at all if I can help it.

WARNING would be suitable if we could classify warnings, e.g.:

{-# WARNING (partial) decodeUtf8 "…" #-}

More information about the Libraries mailing list