Skip to content
This repository was archived by the owner on Jun 15, 2023. It is now read-only.

Fix printers and parsers#24

Merged
natefaubion merged 1 commit into
slamdata:masterfrom
natefaubion:parse-print-fixes
Aug 2, 2017
Merged

Fix printers and parsers#24
natefaubion merged 1 commit into
slamdata:masterfrom
natefaubion:parse-print-fixes

Conversation

@natefaubion
Copy link
Copy Markdown
Collaborator

No description provided.

@natefaubion natefaubion requested a review from garyb August 1, 2017 23:15
Copy link
Copy Markdown
Member

@garyb garyb left a comment

Choose a reason for hiding this comment

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

Looks great. We didn't need to do anything with negative numbers with unary sign in the end?

@natefaubion
Copy link
Copy Markdown
Collaborator Author

I added that here https://github.com/slamdata/purescript-ejson/pull/24/files#diff-516dd23bf6e4c74ab9d4e4b7946bf694L211

But it is not important for the sql-squared parser, since it will always tokenize + and - separately.

@natefaubion natefaubion merged commit c1632be into slamdata:master Aug 2, 2017
@garyb
Copy link
Copy Markdown
Member

garyb commented Aug 2, 2017

I meant during printing actually - since there's the possibility of a negated negative number in the AST. It's only a problem when constructed by means other than the parser though I guess.

@natefaubion
Copy link
Copy Markdown
Collaborator Author

Yes, its a problem if you construct a Negate (-123.456), but the AST is not correct by construction anyway. There are tons of cases like that.

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

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants