Skip to content

Extended infix operators#850

Merged
paf31 merged 2 commits intomasterfrom
839
Feb 8, 2015
Merged

Extended infix operators#850
paf31 merged 2 commits intomasterfrom
839

Conversation

@paf31
Copy link
Copy Markdown
Contributor

@paf31 paf31 commented Feb 8, 2015

@garyb Could you please review this one?

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.01%) to 83.31% when pulling abfdf5a on 839 into 0f54054 on master.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps should name this something other than parseIdentInfix, and update the hint for parsec?

@garyb
Copy link
Copy Markdown
Member

garyb commented Feb 8, 2015

Looks good to me apart from that minor nitpick :)

Will be interesting to see how this pans out. Just because it can be abused doesn't necessarily seem like a reason not to have it either.

👍

@garyb
Copy link
Copy Markdown
Member

garyb commented Feb 8, 2015

I overhauled the syntax guide this morning by the way (I know we promote the book over that stuff now, but it's still valuable as a quick reference I think) so you might want to update that after releasing this too.

@garyb
Copy link
Copy Markdown
Member

garyb commented Feb 8, 2015

Oh, and you might want to tweak the pretty printer for OperatorSection now?

@paf31
Copy link
Copy Markdown
Contributor Author

paf31 commented Feb 8, 2015

All good points, thank you.

@coveralls
Copy link
Copy Markdown

Coverage Status

Coverage decreased (-0.01%) to 83.31% when pulling 6120951 on 839 into 0f54054 on master.

paf31 added a commit that referenced this pull request Feb 8, 2015
Extended infix operators
@paf31 paf31 merged commit 00086aa into master Feb 8, 2015
@paf31 paf31 deleted the 839 branch February 8, 2015 21:53
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is really nice and has great readability -- also easier to explain the `` rule as operating over expressions as opposed to just "identifiers". It would be useful to put a nested example in these tests to demonstrate the parser can handle nesting.

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure thing. Will be nice to get the coverage up as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants