-
Notifications
You must be signed in to change notification settings - Fork 313
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
Duplexer confusing example #104
Comments
+1 on this. The confusing element for me here isn't
Because I didn't realize that At the very least perhaps a heads up to this little twist in |
I also found myself confused as to why
didn't work. |
+1 |
the confusion here stems from the following:
for process you're inside the process to |
+1 The @Sequoia explanation must be in the documentation. |
Thank you @Sequoia for the explanation, I got confused as well. However, even the reference solution doesn't work due to a unit test failing
|
Nice discussion, definitely worth having the explanation from @Sequoia in the exercise to be accessible to anyone going through the problem. Opened a PR to include these additions in the hints. |
Closing since changes was added in #196 |
I'd recommend changing the challenge to use anything else but child_process. Seeing stdin and stdout as the arguments can give people false confidence of duplexer. I just spend an hour trying to figure out the next challenge only to find out that the order of duplexer is Writable, Readable. I know the documentation says that but other people made the same mistake: #55
I'd bet it help other people too if this challenge used process.stdin/stdout instead or something like reading from files.
The text was updated successfully, but these errors were encountered: