We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mostly an annoyance.
Data.ByteString has it, System.IO has it, this has everything but it.
The text was updated successfully, but these errors were encountered:
It's in http://hackage.haskell.org/package/bytestring-0.10.8.2/docs/Data-ByteString-Lazy-Char8.html#v:hPutStrLn
Also notice, it's deprecated in the non-Char8 module: http://hackage.haskell.org/package/bytestring-0.10.8.2/docs/Data-ByteString.html#v:hPutStrLn
Char8
Sorry, something went wrong.
I'm fine with doing nothing about this – the explanation on the deprecation notice makes sense to me.
Deprecated: Use Data.ByteString.Char8.hPutStrLn instead. (Functions that rely on ASCII encodings belong in Data.ByteString.Char8)
For what it is worth I agree that this is expected. Partitioning out the ASCII specific interfaces is a good thing.
I'm in favor of closing this.
No branches or pull requests
Mostly an annoyance.
Data.ByteString has it, System.IO has it, this has everything but it.
The text was updated successfully, but these errors were encountered: