haskell - Typechecking problems with pipes-attoparsec -

-

i've been trying out pipes-attoparsec haven't been having luck.

it appears there type mismatch between void , x in (what seems be) relatively straightforward code. i've read in library (that type synonym @ point), i'm not sure how interpret type error.

test code:

{-# language overloadedstrings,rankntypes #-} module main  import qualified data.attoparsec.char8  import qualified pipes p import qualified pipes.attoparsec pa         import qualified pipes.bytestring pb import qualified pipes.parse  pp  passthrough :: a.parser pb.bytestring passthrough = a.takewhile (\s->true)  f :: monad m => pp.statet (p.producer pb.bytestring m r) m (either string  string) f =   r <- pa.parse passthrough   return $ case r of     left e -> left "a"     right (_,r1) -> right "b"  g = pp.evalstatet f pb.stdin  h = p.runeffect g

this results in error:

p.hs:16:8:     couldn't match type `pipes-4.0.2:pipes.internal.proxy                            data.void.void () () pb.bytestring m r0'                   `p.proxy p.x () () pb.bytestring m r'     expected type: pp.statet                      (pp.producer pb.bytestring m r)                      m                      (either pa.parsingerror (int, pb.bytestring))       actual type: pp.statet                      (pipes-4.0.2:pipes.core.producer pb.bytestring m r0)                      m                      (either pa.parsingerror (int, pb.bytestring))     in return type of call of `pa.parse'     in stmt of 'do' block: r <- pa.parse passthrough     in expression:       { r <- pa.parse passthrough;            return            $ case r of {                left e -> left "a"                right (_, r1) -> right "b" } } failed, modules loaded: none.

you need upgrade latest pipes-attoparsec, restricts pipes dependency 4.1.*. can give more detailed information how might have arisen if list versions have installed pipes, pipes-parse, , pipes-attoparsec. if type ghc-pkg list | grep pipes should enough.


Comments

Post a Comment

Popular posts from this blog

python - Subclassed QStyledItemDelegate ignores Stylesheet -

-
i'm trying subclass qstyleditemdelegate remove focus rectangle in qcombobox . even though i'm calling base implementation of paint function , nothing else, result different. looks if parts of style-sheet influence bounding box of item taken consideration. class pstyleditemdelegate(qstyleditemdelegate): def __init__(self, *args, **kwds): super(pstyleditemdelegate, self).__init__(*args, **kwds) def paint(self, *args, **kwargs): qstyleditemdelegate.paint(*args, **kwargs) what have paint unmodified qstyleditemdelegate ? as suggested tried replacing pyside pyqt4 , works, appears bug. update pyside 1.1.2 1.2.1 result same. unfortunately switch breaks other parts of code, if there no other suggestions i'm going accept answer. edit bug tracked here
Read more

java - HttpClient 3.1 Connection pooling vs HttpClient 4.3.2 -

-
i have used httpclient3.1(java) connection pooling below : import org.apache.commons.httpclient.httpclient; import org.apache.commons.httpclient.multithreadedhttpconnectionmanager; import org.apache.commons.httpclient.params.httpclientparams; import org.apache.commons.httpclient.params.httpmethodparams; import org.apache.log4j.logger; public class httpclientmanager { private static logger logger = logger.getlogger(httpclientmanager.class); private static multithreadedhttpconnectionmanager connectionmanager = new multithreadedhttpconnectionmanager(); private static httpclientparams clientparams = new httpclientparams(); static { try { clientparams.makelenient(); clientparams.setauthenticationpreemptive(false); clientparams.setparameter(httpmethodparams.so_timeout, new integer(30000)); // set so_timeout clientparams.setparameter(httpmethodparams.head_body_check_timeout, new integer(3000)); // head responses ...
Read more

node.js - StackOverflow API not returning JSON -

-
i using node.js script gather data stackoverflow. know responses gzipped, put code in should take care of that. script follows: var request = require('request'); var zlib = require('zlib'); function getstackoverflowresponse(url, callback){ request(url, {encoding: null}, function(err, response, body){ if(response.headers['content-encoding'] == 'gzip'){ zlib.gunzip(body, function(err, dezipped) { callback(dezipped); }); } else { callback(body); } }); } var url = "https://api.stackexchange.com/docs/questions#pagesize=2&order=desc&min=2014-01-04&max=2014-02-02&sort=activity&tagged=apigee&filter=default&site=stackoverflow&run=true"; getstackoverflowresponse(url, function(questions) { console.log(questions); }); instead of getting json output, i'm getting following response: buffer 0d 0a 0d 0a 0d 0a 0d 0a 3c 21 44 4f 43 54 59 50 45 20 48...
Read more