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

LazyDom #617

Open
zslayton opened this issue Jun 9, 2020 · 3 comments
Open

LazyDom #617

zslayton opened this issue Jun 9, 2020 · 3 comments

Comments

@zslayton
Copy link
Contributor

zslayton commented Jun 9, 2020

Rather than materializing the complete tree eagerly, allow users to create a LazyValue that only parses the input buffer as much as is necessary to satisfy the method call at hand.

@jfuehner
Copy link

jfuehner commented Oct 7, 2021

@zslayton any ETA on this? This could be huge for in-browser use/adoption.

@zslayton
Copy link
Contributor Author

zslayton commented Oct 7, 2021

Hi @jfuehner, did you ever get a chance to try the interim solution that I described in issue #594?

I agree that this feature would be great to have. However, this has not yet been prioritized. If anyone is interested in implementing it, I'd be happy to talk through design options.

@jfuehner
Copy link

jfuehner commented Oct 8, 2021

@zslayton thanks for the quick response. In terms of the interim solution are you referring to using a Reader?

I’m sure that would work. Just not ideal from my optic as it would make the client code brittle should a change to the underlying data structure occur from our service. Also, it would mean our client code would need to have a deep understanding of the data structures.

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

No branches or pull requests

2 participants