Vincent Hanquez
Vincent Hanquez
Without a stack trace, not really. the stack trace is about a SIGPIPE, not a SIGSEGV.
I'm pretty sure you need to ignore SIGPIPE in the debugger; the behavior of the program doesn't make a difference as to whether sigpipe get generated or not. it should...
definitely, related to #135
Thanks @parsonsmatt couple of niggle I'll fix on top, but the base seems solid. pretty disappointing to have more breaking changes in the low-level ghc parts again :( side note:...
@mgsloan that's a very interesting approach, given what it offer. It's probably ok given that bytestring, text and other core packages API are so frozen, but it could be a...
There's no moral high grounds here; it's mainly a technical reason at the center point to make stuff that works much better together, the rest is just gravy.
probably useful to see how to mix things, but as a downer using travis hackage deployment is probably going to use cabal, so caveat of no automatic generation of hpack...
thanks. that's really useful !
at the moment there's no way to go faster because it's using the Prelude implementation of lines and filter. relatively easy fix though.
could you try running it through conduit just to check for speed difference ? Something like this should workaround the slow perf of String.lines: ```haskell import Foundation.Conduit.Textual (lines) runConduit (sinkSource...