forked from davidlazar/process-extras
-
Notifications
You must be signed in to change notification settings - Fork 5
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
confusion exception with lazy text encoding error #14
Comments
I'm not too surprised by this, but I'm not sure how to fix it. |
Almost any change to this code makes it strict, I don't have great intuition about this stuff. |
I tried looking at the code but I haven't quite understood it yet; and, yes it is easy to introduce strictness by mistake. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reading a strict text from a process that produces raw bytes fails due to an encoding error and we get a reasonable exception:
However, if we do the same thing with a lazy text, we get an exception relating to hClose rather than the encoding:
In any case the reading succeeds with either strict or lazy bytestrings (because no text encoding is required):
The text was updated successfully, but these errors were encountered: