Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Have JSONValue conform to JSONDecodable #63

Closed
gfontenot opened this issue Feb 24, 2015 · 1 comment · Fixed by #66
Closed

Have JSONValue conform to JSONDecodable #63

gfontenot opened this issue Feb 24, 2015 · 1 comment · Fixed by #66

Comments

@gfontenot
Copy link
Collaborator

If JSONValue conforms to JSONDecodable, we can cut the number of operators we define in half in favor of using chained parsing operators.

j <| ["foo", "bar"] would become j <| "foo" <| "bar"

This would also allow us to get rid of subscript, as well as find probably.

There might be performance implications here.

@gfontenot gfontenot added this to the 1.0.0 - No More Excuses milestone Feb 24, 2015
@kaishin
Copy link

kaishin commented Feb 24, 2015

Thumbs up. The subscript thing is not even intuitive.

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

Successfully merging a pull request may close this issue.

2 participants