Unsafe aspects of ByteString

[Tim Docker]

dons at cse.unsw.edu.au wrote:

> The functions should document this behaviour better. Of course, you're
paying with poke and C strings so you
> should be careful anyway. I'll correct the documentation to explain
all this.

Forgive a non-experts comment:

This approach ("read the doco and be careful when you use these
functions") feels contrary to the haskell ethos of pure code being
reliably pure. What's the argument for not prefixing such functions with
"unsafe"? 

Tim