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

Clarity on laziness #81

Closed
mikera opened this issue Jun 18, 2015 · 1 comment
Closed

Clarity on laziness #81

mikera opened this issue Jun 18, 2015 · 1 comment

Comments

@mikera
Copy link

mikera commented Jun 18, 2015

Hello,

I recently had a problem with parse-stream in cheshire 5.4.0 acting lazily (it caused a "Stream closed" exception because the lazy loading happened outside the scope of the with-open block that created the stream).

Previously, the same code worked (with an earlier version of cheshire) so I assume that something changed with respect to laziness.

The docstring currently says:

"If laziness is needed, see parsed-seq"

That sort of implies that parse-stream is not meant to be lazy.... but the behaviour implies otherwise. Can we get clarity in the docs on whether this is actually meant to be lazy?

@dakrone dakrone closed this as completed in 38ea8bf Jul 4, 2015
@dakrone
Copy link
Owner

dakrone commented Jul 4, 2015

Pushed a commit for this, thanks!

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