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

Some hints on to-string not being lazy #57

Closed
wants to merge 1 commit into from
Closed

Conversation

ieugen
Copy link
Member

@ieugen ieugen commented Jul 13, 2022

@ieugen ieugen requested a review from KingMob as a code owner July 13, 2022 09:23
Copy link
Collaborator

@KingMob KingMob left a comment

Choose a reason for hiding this comment

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

Thanks for this! Couple changes before I can accept:

  1. The top-level byte-streams ns has been deprecated, because in general, a top-level ns is not Java friendly, and in particular, it breaks attempts to use bs with Graal. Be sure to copy/move this to the clj-commons.byte-streams/to-string fn
  2. Let's change "Will consume all input." to "Will consume all the input it can." I don't see a test I can check for the behavior, but I'm pretty sure it will read all the bytes it can, and stop as soon as there's none available, even if more bytes come in later.

ieugen added a commit that referenced this pull request Jul 18, 2022
@ieugen
Copy link
Member Author

ieugen commented Jul 18, 2022

Created new PR.

@ieugen ieugen closed this Jul 18, 2022
@KingMob KingMob deleted the ieugen-patch-1 branch July 20, 2022 07:20
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

Successfully merging this pull request may close these issues.

2 participants