Giter Club home page Giter Club logo

intro_to_parsing's People

Contributors

bitemyapp avatar cris avatar jakewheat avatar nickager avatar sgalal avatar xhliu avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

intro_to_parsing's Issues

incorrect explanation for the associativity of `a <$> b <$> c`

line 196 of ApplicativeStyle.lhs claims that

a <$> b <$> c

is parsed as

a <$> (b <$> c)

This is incorrect:

λ> :info (<$>)
(<$>) :: Functor f => (a -> b) -> f a -> f b
    -- Defined in ‘Data.Functor’
infixl 4 <$>

It actually associates to the left. However here it doesn't matter, since we have

instance Functor ((->) r) -- Defined in ‘GHC.Base’

So essentially we are writing

(a . b) <$> c

which is the same as

a <$> (b <$> c)

due to functor law.

suggest `parseTest` rather than `regularParse`

i was following this guide and i rolled out my simplified versions of the parsing help functions you have here. eventually i found out that i just rewrote parseTest.

by suggesting the users to test with parseTest from the beginning you make the guide way easier to follow because we wouldn't need to clone, compile, etcetera

Typo in 3.6.1

Following 3.6.1 as it is results in:

*Main> regularParse simpleExpr5 "(1+a)"
Left (line 1, column 3):
unexpected "+"
expecting digit or ")"

The expected is:

*Main> parseWithWhitespace simpleExpr5 "(1+a)"
Right (Parens (Add (Num 1) (Var "a")))

I think this happens because:

term5 :: Parser SimpleExpr 
term5 = term term5

simpleExpr5 :: Parser SimpleExpr
simpleExpr5 = try addE5 <|> term5

term5 doesn't know how to parse additions, but simpleExpr5 does. When parsing (1+2), addE5 fails and lets term5 try, which parses the parentheses. But then term5 cannot parse the sub-expression 1+2, hence the error.

On my side, I was able to fix this by doing:

term5 :: Parser SimpleExpr 
term5 = term simpleExpr5

Is this the correct/most elegant fix?

Thanks for putting together such a well-written tutorial on parsec!

Tutorial is out of date

Tutorial on parsec is out of date, doesn't work with current latest Haskell/GHC distribution for various reason. I would be glad to submit a pull request to fix it.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.