#4144: Exception: ToDo: hGetBuf - when using custom handle infrastructure -------------------------------+-------------------------------------------- Reporter: AntoineLatter | Owner: simonmar Type: bug | Status: patch Priority: high | Milestone: 7.8.1 Component: libraries/base | Version: 7.6.1 Resolution: | Keywords: Os: Unknown/Multiple | Architecture: Unknown/Multiple Failure: Runtime crash | Difficulty: Unknown Testcase: | Blockedby: Blocking: | Related: -------------------------------+-------------------------------------------- Comment(by joeyadams): Replying to [comment:15 igloo]:

So what's the proposal here exactly? Is it to deprecate these?: {{{ System.IO.hGetBufSome System.IO.hGetBufNonBlocking System.IO.hPutBufNonBlocking Data.ByteString.hGetNonBlocking Data.ByteString.hPutNonBlocking }}}

There are a couple of uses of `hGetNonBlocking` in haskeline.

No, keep `hGetBufSome`. It's useful for reading lines of text from a socket, without waiting for some arbitrary limit to be reached, and without reading a byte at a time. haskeline only uses `System.IO.hWaitForInput` and `Data.ByteString.hGetNonBlocking` for compatibility with GHC < 7.4.1, which does not have working encoding support (see #5436). Thanks for pointing these out. -- Ticket URL: http://hackage.haskell.org/trac/ghc/ticket/4144#comment:16 GHC http://www.haskell.org/ghc/ The Glasgow Haskell Compiler