On Sun, Mar 15, 2009 at 8:40 PM, Alexander Dunlap <alexander.dunlap@gmail.com> wrote:

I have noticed that in both Data.Binary and Data.Text (which is still
experimental, but still), the "decode" functions can be undefined
(i.e. bottom) if they encounter malformed input.

For decoding Unicode, it's typical to provide a flexible API that can do one of the following on a bad encoding:

Substitute a character
Skip it
Return the partial decode
Throw an exception

I just haven't gotten there yet.