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

Post Release TODOS #8

Open
4 of 12 tasks
gerrymanoim opened this issue Jul 16, 2020 · 2 comments
Open
4 of 12 tasks

Post Release TODOS #8

gerrymanoim opened this issue Jul 16, 2020 · 2 comments

Comments

@gerrymanoim
Copy link
Owner

gerrymanoim commented Jul 16, 2020

  • count for array
  • index for array
  • benchmarks (look at overhead of access vs python directly)
  • Other compiler flags?
  • string padding?
  • extra functions
    • validate_utf8
    • load_many/parse_many
    • load_many/parse_many with threads?
    • case insensitive at?
  • Add reprs to Object and Array
  • Expose versions of libpy_simdjson and simdjson

Note: Right now when iterate we convert everything automatically to python objects. Should we be smarter? Or is that not expected?

@llllllllll
Copy link
Collaborator

llllllllll commented Jul 16, 2020

Note: Right now when iterate we convert everything automatically to python objects.

I think that now that we are using ranges, it would be possible to write a transform that has a shared pointer to the parser so it can convert the Objects and Arrays into our rich objects.

@gerrymanoim
Copy link
Owner Author

Could we use disambiguate_result plus the shared pointer inside the transform?

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

No branches or pull requests

2 participants